WEBVTT Kind: captions Language: en 00:01:45.580 --> 00:01:47.680 align:start position:0% all<00:01:46.580> right<00:01:46.700> we'll<00:01:46.820> call<00:01:47.000> to<00:01:47.180> order<00:01:47.330> the 00:01:47.680 --> 00:01:47.690 align:start position:0% all right we'll call to order the 00:01:47.690 --> 00:01:50.800 align:start position:0% all right we'll call to order the October<00:01:48.320> 19th<00:01:48.830> meeting<00:01:49.600> planning<00:01:50.600> and<00:01:50.780> zoning 00:01:50.800 --> 00:01:50.810 align:start position:0% October 19th meeting planning and zoning 00:01:50.810 --> 00:01:53.080 align:start position:0% October 19th meeting planning and zoning board<00:01:51.320> first<00:01:51.740> order<00:01:52.160> of<00:01:52.190> business<00:01:52.670> is 00:01:53.080 --> 00:01:53.090 align:start position:0% board first order of business is 00:01:53.090 --> 00:01:54.969 align:start position:0% board first order of business is adopting<00:01:53.660> our<00:01:53.869> agenda<00:01:54.320> or<00:01:54.440> amending<00:01:54.860> it 00:01:54.969 --> 00:01:54.979 align:start position:0% adopting our agenda or amending it 00:01:54.979 --> 00:01:58.330 align:start position:0% adopting our agenda or amending it anyone<00:01:55.760> have<00:01:55.910> any<00:01:56.030> changes<00:01:56.570> to<00:01:56.600> the<00:01:56.780> agenda<00:01:57.340> if 00:01:58.330 --> 00:01:58.340 align:start position:0% anyone have any changes to the agenda if 00:01:58.340 --> 00:02:00.520 align:start position:0% anyone have any changes to the agenda if not<00:01:58.610> I'll<00:01:58.790> look<00:01:58.910> for<00:01:59.090> a<00:01:59.119> motion<00:01:59.450> to<00:01:59.570> adopt<00:01:59.780> move 00:02:00.520 --> 00:02:00.530 align:start position:0% not I'll look for a motion to adopt move 00:02:00.530 --> 00:02:03.100 align:start position:0% not I'll look for a motion to adopt move their<00:02:00.680> way<00:02:00.770> about<00:02:00.950> the<00:02:01.130> agenda<00:02:01.460> second<00:02:02.110> any 00:02:03.100 --> 00:02:03.110 align:start position:0% their way about the agenda second any 00:02:03.110 --> 00:02:07.810 align:start position:0% their way about the agenda second any discussion<00:02:03.229> on<00:02:03.970> favor<00:02:05.170> I'd<00:02:06.170> say<00:02:06.650> I<00:02:06.680> all<00:02:07.340> right 00:02:07.810 --> 00:02:07.820 align:start position:0% discussion on favor I'd say I all right 00:02:07.820 --> 00:02:11.130 align:start position:0% discussion on favor I'd say I all right thank<00:02:08.090> you<00:02:08.450> our<00:02:08.830> genders<00:02:09.830> adopted<00:02:10.369> the<00:02:10.520> second 00:02:11.130 --> 00:02:11.140 align:start position:0% thank you our genders adopted the second 00:02:11.140 --> 00:02:13.270 align:start position:0% thank you our genders adopted the second order<00:02:12.140> of<00:02:12.290> business<00:02:12.410> for<00:02:12.800> us<00:02:12.980> is<00:02:13.160> the 00:02:13.270 --> 00:02:13.280 align:start position:0% order of business for us is the 00:02:13.280 --> 00:02:15.010 align:start position:0% order of business for us is the nomination<00:02:13.790> of<00:02:13.880> the<00:02:13.970> vice<00:02:14.209> chair<00:02:14.630> for<00:02:14.900> this 00:02:15.010 --> 00:02:15.020 align:start position:0% nomination of the vice chair for this 00:02:15.020 --> 00:02:17.140 align:start position:0% nomination of the vice chair for this coming<00:02:15.260> term<00:02:15.650> before<00:02:16.130> I<00:02:16.340> do<00:02:16.459> that<00:02:16.610> I<00:02:16.790> want<00:02:17.000> to 00:02:17.140 --> 00:02:17.150 align:start position:0% coming term before I do that I want to 00:02:17.150 --> 00:02:18.790 align:start position:0% coming term before I do that I want to say<00:02:17.330> hello<00:02:17.540> and<00:02:17.750> welcome<00:02:18.080> to<00:02:18.230> our<00:02:18.260> two<00:02:18.620> new 00:02:18.790 --> 00:02:18.800 align:start position:0% say hello and welcome to our two new 00:02:18.800 --> 00:02:21.280 align:start position:0% say hello and welcome to our two new members<00:02:18.980> and<00:02:19.810> identify<00:02:20.810> then<00:02:20.930> we<00:02:21.020> have<00:02:21.110> dan 00:02:21.280 --> 00:02:21.290 align:start position:0% members and identify then we have dan 00:02:21.290 --> 00:02:24.250 align:start position:0% members and identify then we have dan mcpharlin<00:02:21.500> to<00:02:21.950> my<00:02:22.070> right<00:02:22.660> Sally<00:02:23.660> Hansen<00:02:24.110> is 00:02:24.250 --> 00:02:24.260 align:start position:0% mcpharlin to my right Sally Hansen is 00:02:24.260 --> 00:02:26.020 align:start position:0% mcpharlin to my right Sally Hansen is not<00:02:24.440> here<00:02:24.680> but<00:02:24.709> she's<00:02:25.040> also<00:02:25.250> one<00:02:25.580> of<00:02:25.610> our<00:02:25.850> our 00:02:26.020 --> 00:02:26.030 align:start position:0% not here but she's also one of our our 00:02:26.030 --> 00:02:28.840 align:start position:0% not here but she's also one of our our newer<00:02:26.690> members<00:02:27.190> with<00:02:28.190> two<00:02:28.370> new<00:02:28.489> members<00:02:28.640> on 00:02:28.840 --> 00:02:28.850 align:start position:0% newer members with two new members on 00:02:28.850 --> 00:02:30.820 align:start position:0% newer members with two new members on the<00:02:28.940> board<00:02:28.970> this<00:02:29.270> year<00:02:29.330> so<00:02:29.870> with<00:02:30.470> that<00:02:30.620> in<00:02:30.800> mind 00:02:30.820 --> 00:02:30.830 align:start position:0% the board this year so with that in mind 00:02:30.830 --> 00:02:33.790 align:start position:0% the board this year so with that in mind I<00:02:31.310> will<00:02:31.640> entertain<00:02:32.420> a<00:02:32.600> motion<00:02:32.720> if<00:02:33.290> anyone<00:02:33.650> has 00:02:33.790 --> 00:02:33.800 align:start position:0% I will entertain a motion if anyone has 00:02:33.800 --> 00:02:36.040 align:start position:0% I will entertain a motion if anyone has a<00:02:33.830> recommendation<00:02:34.310> or<00:02:34.640> a<00:02:34.700> nomination<00:02:35.090> for<00:02:35.239> our 00:02:36.040 --> 00:02:36.050 align:start position:0% a recommendation or a nomination for our 00:02:36.050 --> 00:02:38.380 align:start position:0% a recommendation or a nomination for our vice<00:02:36.680> chair<00:02:37.010> well<00:02:37.220> mon<00:02:37.400> is<00:02:37.550> not<00:02:37.730> here<00:02:37.880> so<00:02:38.060> i<00:02:38.090> say 00:02:38.380 --> 00:02:38.390 align:start position:0% vice chair well mon is not here so i say 00:02:38.390 --> 00:02:43.180 align:start position:0% vice chair well mon is not here so i say mom<00:02:39.100> no<00:02:40.100> serious<00:02:40.730> yeah<00:02:41.390> I<00:02:41.950> would<00:02:42.950> be<00:02:43.160> very 00:02:43.180 --> 00:02:43.190 align:start position:0% mom no serious yeah I would be very 00:02:43.190 --> 00:02:45.820 align:start position:0% mom no serious yeah I would be very pleased<00:02:43.820> to<00:02:44.180> nominate<00:02:44.540> our<00:02:45.110> fellow<00:02:45.470> board 00:02:45.820 --> 00:02:45.830 align:start position:0% pleased to nominate our fellow board 00:02:45.830 --> 00:02:49.060 align:start position:0% pleased to nominate our fellow board member<00:02:46.190> Mona<00:02:46.970> here<00:02:47.239> it's<00:02:47.540> best<00:02:47.930> for<00:02:48.350> vice 00:02:49.060 --> 00:02:49.070 align:start position:0% member Mona here it's best for vice 00:02:49.070 --> 00:02:52.960 align:start position:0% member Mona here it's best for vice chair<00:02:49.400> I<00:02:49.720> second<00:02:50.720> that<00:02:50.750> in<00:02:51.140> a<00:02:51.200> second<00:02:51.590> I<00:02:51.970> should 00:02:52.960 --> 00:02:52.970 align:start position:0% chair I second that in a second I should 00:02:52.970 --> 00:02:54.610 align:start position:0% chair I second that in a second I should point<00:02:53.120> out<00:02:53.269> that<00:02:53.450> while<00:02:53.780> Mona<00:02:54.049> is<00:02:54.200> not<00:02:54.380> here 00:02:54.610 --> 00:02:54.620 align:start position:0% point out that while Mona is not here 00:02:54.620 --> 00:02:56.560 align:start position:0% point out that while Mona is not here she<00:02:54.830> is<00:02:54.980> eligible<00:02:55.160> to<00:02:55.489> be<00:02:55.640> nominated<00:02:56.360> for<00:02:56.480> vice 00:02:56.560 --> 00:02:56.570 align:start position:0% she is eligible to be nominated for vice 00:02:56.570 --> 00:03:00.550 align:start position:0% she is eligible to be nominated for vice chairs<00:02:56.959> there<00:02:57.110> any<00:02:57.230> discussion<00:02:57.320> on<00:02:57.709> that<00:02:59.560> then 00:03:00.550 --> 00:03:00.560 align:start position:0% chairs there any discussion on that then 00:03:00.560 --> 00:03:02.710 align:start position:0% chairs there any discussion on that then would<00:03:01.070> those<00:03:01.250> of<00:03:01.459> you<00:03:01.580> in<00:03:01.730> favor<00:03:01.970> of<00:03:02.120> that<00:03:02.239> of 00:03:02.710 --> 00:03:02.720 align:start position:0% would those of you in favor of that of 00:03:02.720 --> 00:03:05.170 align:start position:0% would those of you in favor of that of naming<00:03:03.260> Mona<00:03:03.470> our<00:03:03.680> vice<00:03:03.920> chair<00:03:04.280> please<00:03:04.579> say 00:03:05.170 --> 00:03:05.180 align:start position:0% naming Mona our vice chair please say 00:03:05.180 --> 00:03:08.670 align:start position:0% naming Mona our vice chair please say aye<00:03:05.530> any<00:03:06.530> opposed<00:03:07.030> thank<00:03:08.030> you<00:03:08.180> and 00:03:08.670 --> 00:03:08.680 align:start position:0% aye any opposed thank you and 00:03:08.680 --> 00:03:11.430 align:start position:0% aye any opposed thank you and congratulations<00:03:09.680> Mona<00:03:10.160> wherever<00:03:10.519> you<00:03:10.700> are 00:03:11.430 --> 00:03:11.440 align:start position:0% congratulations Mona wherever you are 00:03:11.440 --> 00:03:14.920 align:start position:0% congratulations Mona wherever you are some<00:03:12.440> island<00:03:12.829> somewhere<00:03:12.920> lucky<00:03:13.489> girl<00:03:13.870> you<00:03:14.870> are 00:03:14.920 --> 00:03:14.930 align:start position:0% some island somewhere lucky girl you are 00:03:14.930 --> 00:03:20.110 align:start position:0% some island somewhere lucky girl you are now<00:03:15.110> the<00:03:15.140> vice<00:03:15.410> chair<00:03:18.010> our<00:03:19.010> next<00:03:19.340> item<00:03:19.489> is<00:03:19.790> the 00:03:20.110 --> 00:03:20.120 align:start position:0% now the vice chair our next item is the 00:03:20.120 --> 00:03:22.060 align:start position:0% now the vice chair our next item is the approval<00:03:20.150> of<00:03:20.600> our<00:03:20.750> minutes<00:03:21.079> we<00:03:21.410> have<00:03:21.530> two<00:03:21.799> sets 00:03:22.060 --> 00:03:22.070 align:start position:0% approval of our minutes we have two sets 00:03:22.070 --> 00:03:23.830 align:start position:0% approval of our minutes we have two sets of<00:03:22.220> minutes<00:03:22.519> coming<00:03:22.790> up<00:03:22.970> by<00:03:23.209> one<00:03:23.450> for<00:03:23.720> the 00:03:23.830 --> 00:03:23.840 align:start position:0% of minutes coming up by one for the 00:03:23.840 --> 00:03:26.380 align:start position:0% of minutes coming up by one for the fifteenth<00:03:24.470> of<00:03:24.680> September<00:03:25.549> work<00:03:25.730> session<00:03:26.239> and 00:03:26.380 --> 00:03:26.390 align:start position:0% fifteenth of September work session and 00:03:26.390 --> 00:03:28.479 align:start position:0% fifteenth of September work session and one<00:03:26.870> for<00:03:27.049> the<00:03:27.110> 21st<00:03:27.650> to<00:03:27.799> September<00:03:28.310> our 00:03:28.479 --> 00:03:28.489 align:start position:0% one for the 21st to September our 00:03:28.489 --> 00:03:32.460 align:start position:0% one for the 21st to September our regular<00:03:28.940> meeting<00:03:30.010> does<00:03:31.010> anyone<00:03:31.190> have<00:03:31.430> any 00:03:32.460 --> 00:03:32.470 align:start position:0% regular meeting does anyone have any 00:03:32.470 --> 00:03:35.229 align:start position:0% regular meeting does anyone have any changes<00:03:33.470> amendments<00:03:34.040> edits<00:03:34.340> to<00:03:34.489> either<00:03:34.820> of 00:03:35.229 --> 00:03:35.239 align:start position:0% changes amendments edits to either of 00:03:35.239 --> 00:03:38.080 align:start position:0% changes amendments edits to either of those<00:03:35.420> sets<00:03:35.750> of<00:03:35.930> minutes<00:03:36.230> I<00:03:36.670> think<00:03:37.670> we<00:03:37.790> have<00:03:37.820> to 00:03:38.080 --> 00:03:38.090 align:start position:0% those sets of minutes I think we have to 00:03:38.090 --> 00:03:40.030 align:start position:0% those sets of minutes I think we have to take<00:03:38.269> these<00:03:38.480> separately<00:03:38.959> is<00:03:39.350> that<00:03:39.530> correct<00:03:39.709> we 00:03:40.030 --> 00:03:40.040 align:start position:0% take these separately is that correct we 00:03:40.040 --> 00:03:41.680 align:start position:0% take these separately is that correct we can<00:03:40.160> do<00:03:40.280> them<00:03:40.370> both<00:03:40.489> together<00:03:40.730> so<00:03:41.180> if<00:03:41.480> someone 00:03:41.680 --> 00:03:41.690 align:start position:0% can do them both together so if someone 00:03:41.690 --> 00:03:43.569 align:start position:0% can do them both together so if someone wants<00:03:41.989> to<00:03:42.079> move<00:03:42.230> to<00:03:42.290> approve<00:03:42.650> both<00:03:43.040> sets<00:03:43.340> at 00:03:43.569 --> 00:03:43.579 align:start position:0% wants to move to approve both sets at 00:03:43.579 --> 00:03:48.440 align:start position:0% wants to move to approve both sets at one<00:03:43.760> time<00:03:44.530> we<00:03:45.530> can<00:03:45.709> do<00:03:45.860> so<00:03:46.629> so<00:03:47.629> move 00:03:48.440 --> 00:03:48.450 align:start position:0% one time we can do so so move 00:03:48.450 --> 00:03:51.199 align:start position:0% one time we can do so so move give<00:03:48.840> the<00:03:48.989> motion<00:03:49.349> second<00:03:49.800> any<00:03:50.640> discussion<00:03:50.670> on 00:03:51.199 --> 00:03:51.209 align:start position:0% give the motion second any discussion on 00:03:51.209 --> 00:03:53.479 align:start position:0% give the motion second any discussion on the<00:03:51.270> minutes<00:03:51.800> all<00:03:52.800> those<00:03:53.010> in<00:03:53.069> favor<00:03:53.220> of 00:03:53.479 --> 00:03:53.489 align:start position:0% the minutes all those in favor of 00:03:53.489 --> 00:03:54.949 align:start position:0% the minutes all those in favor of adopting<00:03:53.670> both<00:03:54.120> sets<00:03:54.360> of<00:03:54.450> minutes<00:03:54.750> and 00:03:54.949 --> 00:03:54.959 align:start position:0% adopting both sets of minutes and 00:03:54.959 --> 00:03:57.860 align:start position:0% adopting both sets of minutes and improving<00:03:55.319> them<00:03:55.530> say<00:03:55.709> I<00:03:55.739> please<00:03:56.420> thank<00:03:57.420> you<00:03:57.599> we 00:03:57.860 --> 00:03:57.870 align:start position:0% improving them say I please thank you we 00:03:57.870 --> 00:03:59.900 align:start position:0% improving them say I please thank you we are<00:03:58.019> moving<00:03:58.230> right<00:03:58.590> along<00:03:58.739> tonight<00:03:59.310> we<00:03:59.610> have 00:03:59.900 --> 00:03:59.910 align:start position:0% are moving right along tonight we have 00:03:59.910 --> 00:04:03.559 align:start position:0% are moving right along tonight we have no<00:04:00.209> public<00:04:00.690> hearings<00:04:01.459> we<00:04:02.459> do<00:04:02.700> have<00:04:02.970> a<00:04:03.000> case 00:04:03.559 --> 00:04:03.569 align:start position:0% no public hearings we do have a case 00:04:03.569 --> 00:04:05.839 align:start position:0% no public hearings we do have a case without<00:04:03.810> a<00:04:04.110> public<00:04:04.650> hearing<00:04:04.830> so<00:04:05.459> rather<00:04:05.670> than 00:04:05.839 --> 00:04:05.849 align:start position:0% without a public hearing so rather than 00:04:05.849 --> 00:04:07.699 align:start position:0% without a public hearing so rather than go<00:04:06.000> through<00:04:06.030> the<00:04:06.530> instructions<00:04:07.530> for<00:04:07.590> how 00:04:07.699 --> 00:04:07.709 align:start position:0% go through the instructions for how 00:04:07.709 --> 00:04:09.350 align:start position:0% go through the instructions for how public<00:04:08.220> hearing<00:04:08.459> work<00:04:08.670> I'll<00:04:08.880> just<00:04:08.910> mention 00:04:09.350 --> 00:04:09.360 align:start position:0% public hearing work I'll just mention 00:04:09.360 --> 00:04:13.280 align:start position:0% public hearing work I'll just mention that<00:04:10.319> we<00:04:10.620> will<00:04:10.830> introduce<00:04:11.069> this<00:04:12.290> land 00:04:13.280 --> 00:04:13.290 align:start position:0% that we will introduce this land 00:04:13.290 --> 00:04:15.199 align:start position:0% that we will introduce this land development<00:04:13.800> ordinance<00:04:14.099> text<00:04:14.640> amendment<00:04:15.090> and 00:04:15.199 --> 00:04:15.209 align:start position:0% development ordinance text amendment and 00:04:15.209 --> 00:04:17.930 align:start position:0% development ordinance text amendment and then<00:04:15.660> we<00:04:15.900> will<00:04:16.079> discuss<00:04:16.470> it<00:04:16.680> ask<00:04:17.340> questions 00:04:17.930 --> 00:04:17.940 align:start position:0% then we will discuss it ask questions 00:04:17.940 --> 00:04:19.940 align:start position:0% then we will discuss it ask questions and<00:04:18.239> and<00:04:18.600> we<00:04:19.079> will<00:04:19.169> take<00:04:19.350> an<00:04:19.500> action<00:04:19.650> after 00:04:19.940 --> 00:04:19.950 align:start position:0% and and we will take an action after 00:04:19.950 --> 00:04:23.980 align:start position:0% and and we will take an action after that<00:04:20.299> good<00:04:21.299> evening<00:04:21.450> miss<00:04:21.720> bear<00:04:21.900> good<00:04:22.440> evening 00:04:23.980 --> 00:04:23.990 align:start position:0% that good evening miss bear good evening 00:04:23.990 --> 00:04:26.810 align:start position:0% that good evening miss bear good evening tonight<00:04:24.990> before<00:04:25.380> you<00:04:25.620> is<00:04:25.889> consideration<00:04:26.700> of 00:04:26.810 --> 00:04:26.820 align:start position:0% tonight before you is consideration of 00:04:26.820 --> 00:04:29.290 align:start position:0% tonight before you is consideration of to<00:04:27.060> land<00:04:27.419> development<00:04:27.990> ordinance<00:04:28.200> amendments 00:04:29.290 --> 00:04:29.300 align:start position:0% to land development ordinance amendments 00:04:29.300 --> 00:04:32.719 align:start position:0% to land development ordinance amendments these<00:04:30.300> include<00:04:30.930> item<00:04:31.889> a<00:04:32.070> relates<00:04:32.550> to 00:04:32.719 --> 00:04:32.729 align:start position:0% these include item a relates to 00:04:32.729 --> 00:04:35.300 align:start position:0% these include item a relates to connectivity<00:04:33.240> and<00:04:33.690> item<00:04:33.960> C<00:04:34.200> relates<00:04:34.979> to<00:04:35.160> low 00:04:35.300 --> 00:04:35.310 align:start position:0% connectivity and item C relates to low 00:04:35.310 --> 00:04:37.010 align:start position:0% connectivity and item C relates to low density<00:04:35.760> residential<00:04:36.210> development 00:04:37.010 --> 00:04:37.020 align:start position:0% density residential development 00:04:37.020 --> 00:04:42.020 align:start position:0% density residential development standards<00:04:39.350> these<00:04:40.350> items<00:04:40.680> were<00:04:41.160> discussed<00:04:41.820> at 00:04:42.020 --> 00:04:42.030 align:start position:0% standards these items were discussed at 00:04:42.030 --> 00:04:44.090 align:start position:0% standards these items were discussed at your<00:04:42.180> work<00:04:42.389> session<00:04:42.900> on<00:04:43.080> sep<00:04:43.290> tember<00:04:43.500> 15th 00:04:44.090 --> 00:04:44.100 align:start position:0% your work session on sep tember 15th 00:04:44.100 --> 00:04:46.250 align:start position:0% your work session on sep tember 15th they<00:04:44.490> went<00:04:44.790> to<00:04:44.970> a<00:04:45.300> town<00:04:45.510> council<00:04:45.960> public 00:04:46.250 --> 00:04:46.260 align:start position:0% they went to a town council public 00:04:46.260 --> 00:04:49.430 align:start position:0% they went to a town council public hearing<00:04:46.620> and<00:04:46.740> August<00:04:47.250> and<00:04:47.990> following<00:04:48.990> a 00:04:49.430 --> 00:04:49.440 align:start position:0% hearing and August and following a 00:04:49.440 --> 00:04:51.230 align:start position:0% hearing and August and following a recommendation<00:04:50.100> tonight<00:04:50.790> they<00:04:50.970> will<00:04:51.060> move 00:04:51.230 --> 00:04:51.240 align:start position:0% recommendation tonight they will move 00:04:51.240 --> 00:04:53.210 align:start position:0% recommendation tonight they will move forward<00:04:51.479> to<00:04:51.840> town<00:04:52.050> council<00:04:52.560> for<00:04:52.740> a<00:04:52.770> decision 00:04:53.210 --> 00:04:53.220 align:start position:0% forward to town council for a decision 00:04:53.220 --> 00:04:58.159 align:start position:0% forward to town council for a decision in<00:04:53.340> November<00:04:55.880> I'll<00:04:56.880> go<00:04:57.060> through<00:04:57.840> each<00:04:57.990> of 00:04:58.159 --> 00:04:58.169 align:start position:0% in November I'll go through each of 00:04:58.169 --> 00:05:00.230 align:start position:0% in November I'll go through each of these<00:04:58.320> briefly<00:04:59.130> and<00:04:59.340> then<00:04:59.430> staff<00:04:59.970> will<00:05:00.150> be 00:05:00.230 --> 00:05:00.240 align:start position:0% these briefly and then staff will be 00:05:00.240 --> 00:05:03.100 align:start position:0% these briefly and then staff will be available<00:05:00.510> for<00:05:00.750> questions<00:05:01.430> the<00:05:02.430> first<00:05:02.700> item 00:05:03.100 --> 00:05:03.110 align:start position:0% available for questions the first item 00:05:03.110 --> 00:05:06.770 align:start position:0% available for questions the first item related<00:05:04.110> to<00:05:04.229> connectivity<00:05:05.360> would<00:05:06.360> provide 00:05:06.770 --> 00:05:06.780 align:start position:0% related to connectivity would provide 00:05:06.780 --> 00:05:08.930 align:start position:0% related to connectivity would provide greater<00:05:07.200> flexibility<00:05:08.070> for<00:05:08.310> considering 00:05:08.930 --> 00:05:08.940 align:start position:0% greater flexibility for considering 00:05:08.940 --> 00:05:12.350 align:start position:0% greater flexibility for considering connections<00:05:09.740> between<00:05:10.910> streets<00:05:11.910> and<00:05:12.180> new 00:05:12.350 --> 00:05:12.360 align:start position:0% connections between streets and new 00:05:12.360 --> 00:05:14.870 align:start position:0% connections between streets and new developments<00:05:13.200> and<00:05:13.380> existing<00:05:14.310> neighborhoods 00:05:14.870 --> 00:05:14.880 align:start position:0% developments and existing neighborhoods 00:05:14.880 --> 00:05:17.600 align:start position:0% developments and existing neighborhoods that<00:05:15.090> are<00:05:15.150> adjacent<00:05:15.270> and<00:05:15.900> provides<00:05:16.860> the 00:05:17.600 --> 00:05:17.610 align:start position:0% that are adjacent and provides the 00:05:17.610 --> 00:05:19.969 align:start position:0% that are adjacent and provides the option<00:05:17.789> for<00:05:18.300> some<00:05:18.539> decisions<00:05:19.320> to<00:05:19.470> be<00:05:19.620> made<00:05:19.650> at 00:05:19.969 --> 00:05:19.979 align:start position:0% option for some decisions to be made at 00:05:19.979 --> 00:05:22.100 align:start position:0% option for some decisions to be made at the<00:05:20.100> time<00:05:20.130> of<00:05:20.460> the<00:05:20.550> rezoning<00:05:21.110> through 00:05:22.100 --> 00:05:22.110 align:start position:0% the time of the rezoning through 00:05:22.110 --> 00:05:25.159 align:start position:0% the time of the rezoning through rezoning<00:05:22.620> through<00:05:23.220> zoning<00:05:23.400> conditions<00:05:24.169> as 00:05:25.159 --> 00:05:25.169 align:start position:0% rezoning through zoning conditions as 00:05:25.169 --> 00:05:28.990 align:start position:0% rezoning through zoning conditions as opposed<00:05:25.710> to<00:05:27.229> buy<00:05:28.229> the<00:05:28.289> Town<00:05:28.860> Council 00:05:28.990 --> 00:05:29.000 align:start position:0% opposed to buy the Town Council 00:05:29.000 --> 00:05:30.680 align:start position:0% opposed to buy the Town Council typically<00:05:30.000> through<00:05:30.240> a<00:05:30.270> quasi<00:05:30.539> judicial 00:05:30.680 --> 00:05:30.690 align:start position:0% typically through a quasi judicial 00:05:30.690 --> 00:05:34.129 align:start position:0% typically through a quasi judicial hearing<00:05:31.530> at<00:05:31.860> the<00:05:32.010> time<00:05:32.220> of<00:05:32.490> a<00:05:32.780> site<00:05:33.780> plan<00:05:33.810> or 00:05:34.129 --> 00:05:34.139 align:start position:0% hearing at the time of a site plan or 00:05:34.139 --> 00:05:37.670 align:start position:0% hearing at the time of a site plan or subdivision<00:05:34.740> approval<00:05:35.810> would<00:05:36.810> like<00:05:37.320> to<00:05:37.470> point 00:05:37.670 --> 00:05:37.680 align:start position:0% subdivision approval would like to point 00:05:37.680 --> 00:05:40.480 align:start position:0% subdivision approval would like to point out<00:05:37.860> this<00:05:38.099> issue<00:05:38.370> has<00:05:38.729> been<00:05:39.000> discussed<00:05:39.510> it<00:05:39.780> two 00:05:40.480 --> 00:05:40.490 align:start position:0% out this issue has been discussed it two 00:05:40.490 --> 00:05:43.010 align:start position:0% out this issue has been discussed it two public<00:05:41.490> hearings<00:05:41.520> before<00:05:42.120> town<00:05:42.479> council 00:05:43.010 --> 00:05:43.020 align:start position:0% public hearings before town council 00:05:43.020 --> 00:05:44.839 align:start position:0% public hearings before town council there's<00:05:43.169> quite<00:05:43.410> a<00:05:43.440> history<00:05:44.370> that<00:05:44.639> goes<00:05:44.669> back 00:05:44.839 --> 00:05:44.849 align:start position:0% there's quite a history that goes back 00:05:44.849 --> 00:05:49.219 align:start position:0% there's quite a history that goes back to<00:05:45.539> April<00:05:46.169> of<00:05:46.460> 2014<00:05:47.460> where<00:05:48.330> Town<00:05:48.660> Council 00:05:49.219 --> 00:05:49.229 align:start position:0% to April of 2014 where Town Council 00:05:49.229 --> 00:05:50.930 align:start position:0% to April of 2014 where Town Council directed<00:05:49.770> staff<00:05:50.010> to<00:05:50.070> look<00:05:50.430> at<00:05:50.580> this<00:05:50.700> issue 00:05:50.930 --> 00:05:50.940 align:start position:0% directed staff to look at this issue 00:05:50.940 --> 00:05:55.000 align:start position:0% directed staff to look at this issue after<00:05:52.610> having<00:05:53.610> a<00:05:53.669> lot<00:05:53.849> of<00:05:53.970> comments<00:05:54.450> from 00:05:55.000 --> 00:05:55.010 align:start position:0% after having a lot of comments from 00:05:55.010 --> 00:05:57.170 align:start position:0% after having a lot of comments from neighbors<00:05:56.010> as<00:05:56.250> new<00:05:56.430> developments<00:05:57.060> were 00:05:57.170 --> 00:05:57.180 align:start position:0% neighbors as new developments were 00:05:57.180 --> 00:05:59.180 align:start position:0% neighbors as new developments were coming<00:05:57.539> in<00:05:57.720> and<00:05:57.990> making<00:05:58.440> those<00:05:58.919> decisions 00:05:59.180 --> 00:05:59.190 align:start position:0% coming in and making those decisions 00:05:59.190 --> 00:06:00.970 align:start position:0% coming in and making those decisions with<00:05:59.940> Street 00:06:00.970 --> 00:06:00.980 align:start position:0% with Street 00:06:00.980 --> 00:06:04.890 align:start position:0% with Street connections<00:06:01.540> so<00:06:02.890> following<00:06:03.890> this<00:06:04.490> being 00:06:04.890 --> 00:06:04.900 align:start position:0% connections so following this being 00:06:04.900 --> 00:06:07.660 align:start position:0% connections so following this being brought<00:06:05.900> to<00:06:06.110> staffs<00:06:06.380> attention<00:06:07.040> formally<00:06:07.520> by 00:06:07.660 --> 00:06:07.670 align:start position:0% brought to staffs attention formally by 00:06:07.670 --> 00:06:11.830 align:start position:0% brought to staffs attention formally by council<00:06:08.180> in<00:06:08.300> april<00:06:08.660> of<00:06:08.750> 2014<00:06:09.910> was<00:06:10.910> discussed 00:06:11.830 --> 00:06:11.840 align:start position:0% council in april of 2014 was discussed 00:06:11.840 --> 00:06:14.110 align:start position:0% council in april of 2014 was discussed at<00:06:12.110> a<00:06:12.140> work<00:06:12.500> session<00:06:12.800> a<00:06:13.340> council<00:06:13.700> work<00:06:14.090> session 00:06:14.110 --> 00:06:14.120 align:start position:0% at a work session a council work session 00:06:14.120 --> 00:06:20.050 align:start position:0% at a work session a council work session on<00:06:14.870> december<00:06:15.590> 9<00:06:16.490> 2014<00:06:18.310> that<00:06:19.310> was<00:06:19.520> followed<00:06:19.910> up 00:06:20.050 --> 00:06:20.060 align:start position:0% on december 9 2014 that was followed up 00:06:20.060 --> 00:06:22.630 align:start position:0% on december 9 2014 that was followed up with<00:06:20.120> the<00:06:20.450> public<00:06:20.840> hearing<00:06:21.110> in<00:06:21.470> march<00:06:21.800> of<00:06:22.190> this 00:06:22.630 --> 00:06:22.640 align:start position:0% with the public hearing in march of this 00:06:22.640 --> 00:06:25.810 align:start position:0% with the public hearing in march of this year<00:06:22.700> at<00:06:23.180> that<00:06:24.110> time<00:06:24.470> with<00:06:25.340> the<00:06:25.460> public 00:06:25.810 --> 00:06:25.820 align:start position:0% year at that time with the public 00:06:25.820 --> 00:06:28.480 align:start position:0% year at that time with the public hearing<00:06:26.090> there<00:06:26.600> were<00:06:26.780> still<00:06:27.770> some<00:06:27.980> concerns 00:06:28.480 --> 00:06:28.490 align:start position:0% hearing there were still some concerns 00:06:28.490 --> 00:06:31.570 align:start position:0% hearing there were still some concerns from<00:06:28.960> town<00:06:29.960> council<00:06:30.530> so<00:06:30.710> that<00:06:30.890> was<00:06:31.100> sent<00:06:31.340> back 00:06:31.570 --> 00:06:31.580 align:start position:0% from town council so that was sent back 00:06:31.580 --> 00:06:34.240 align:start position:0% from town council so that was sent back to<00:06:31.640> another<00:06:32.510> council<00:06:33.350> work<00:06:33.530> session<00:06:33.560> which 00:06:34.240 --> 00:06:34.250 align:start position:0% to another council work session which 00:06:34.250 --> 00:06:37.570 align:start position:0% to another council work session which took<00:06:34.490> place<00:06:34.550> in<00:06:35.240> july<00:06:35.660> and<00:06:36.070> then<00:06:37.070> following 00:06:37.570 --> 00:06:37.580 align:start position:0% took place in july and then following 00:06:37.580 --> 00:06:40.390 align:start position:0% took place in july and then following the<00:06:38.030> july<00:06:38.690> work<00:06:38.960> session<00:06:39.530> there<00:06:39.800> was<00:06:39.920> a<00:06:39.950> second 00:06:40.390 --> 00:06:40.400 align:start position:0% the july work session there was a second 00:06:40.400 --> 00:06:43.360 align:start position:0% the july work session there was a second public<00:06:40.730> hearing<00:06:41.120> again<00:06:41.500> that<00:06:42.500> was<00:06:42.710> in<00:06:42.890> august 00:06:43.360 --> 00:06:43.370 align:start position:0% public hearing again that was in august 00:06:43.370 --> 00:06:47.350 align:start position:0% public hearing again that was in august of<00:06:43.670> this<00:06:43.850> year<00:06:43.910> and<00:06:45.010> that<00:06:46.010> version<00:06:46.910> that<00:06:47.300> was 00:06:47.350 --> 00:06:47.360 align:start position:0% of this year and that version that was 00:06:47.360 --> 00:06:49.210 align:start position:0% of this year and that version that was presented<00:06:47.870> at<00:06:47.990> the<00:06:48.020> august<00:06:48.470> public<00:06:48.830> hearing 00:06:49.210 --> 00:06:49.220 align:start position:0% presented at the august public hearing 00:06:49.220 --> 00:06:50.920 align:start position:0% presented at the august public hearing is<00:06:49.310> what's<00:06:49.550> before<00:06:49.940> you<00:06:50.060> tonight<00:06:50.240> and<00:06:50.780> that 00:06:50.920 --> 00:06:50.930 align:start position:0% is what's before you tonight and that 00:06:50.930 --> 00:06:54.100 align:start position:0% is what's before you tonight and that was<00:06:51.170> also<00:06:51.920> what<00:06:52.160> was<00:06:52.370> discussed<00:06:53.270> by<00:06:53.630> the<00:06:53.660> board 00:06:54.100 --> 00:06:54.110 align:start position:0% was also what was discussed by the board 00:06:54.110 --> 00:06:58.150 align:start position:0% was also what was discussed by the board members<00:06:54.500> that<00:06:54.740> were<00:06:55.060> seated<00:06:56.060> as<00:06:56.780> of<00:06:57.350> semoran 00:06:58.150 --> 00:06:58.160 align:start position:0% members that were seated as of semoran 00:06:58.160 --> 00:07:00.850 align:start position:0% members that were seated as of semoran September<00:06:58.970> 15th<00:06:59.540> so<00:07:00.140> that<00:07:00.320> just<00:07:00.530> gives<00:07:00.590> a 00:07:00.850 --> 00:07:00.860 align:start position:0% September 15th so that just gives a 00:07:00.860 --> 00:07:03.400 align:start position:0% September 15th so that just gives a little<00:07:01.010> bit<00:07:01.130> of<00:07:01.430> history<00:07:02.270> of<00:07:02.420> that<00:07:02.570> project<00:07:02.810> or 00:07:03.400 --> 00:07:03.410 align:start position:0% little bit of history of that project or 00:07:03.410 --> 00:07:07.180 align:start position:0% little bit of history of that project or this<00:07:03.730> request<00:07:04.730> it<00:07:05.000> does<00:07:05.180> have<00:07:06.070> quite<00:07:07.070> a 00:07:07.180 --> 00:07:07.190 align:start position:0% this request it does have quite a 00:07:07.190 --> 00:07:09.010 align:start position:0% this request it does have quite a lengthy<00:07:07.460> history<00:07:07.820> as<00:07:08.150> that<00:07:08.330> has<00:07:08.510> evolved<00:07:08.930> over 00:07:09.010 --> 00:07:09.020 align:start position:0% lengthy history as that has evolved over 00:07:09.020 --> 00:07:15.490 align:start position:0% lengthy history as that has evolved over time<00:07:12.850> currently<00:07:14.050> connections<00:07:15.050> to<00:07:15.200> adjacent 00:07:15.490 --> 00:07:15.500 align:start position:0% time currently connections to adjacent 00:07:15.500 --> 00:07:17.950 align:start position:0% time currently connections to adjacent neighborhoods<00:07:16.220> are<00:07:16.370> generally<00:07:16.760> required<00:07:16.960> for 00:07:17.950 --> 00:07:17.960 align:start position:0% neighborhoods are generally required for 00:07:17.960 --> 00:07:20.110 align:start position:0% neighborhoods are generally required for all<00:07:17.990> developments<00:07:18.800> and<00:07:18.950> they're<00:07:19.700> addressed 00:07:20.110 --> 00:07:20.120 align:start position:0% all developments and they're addressed 00:07:20.120 --> 00:07:22.720 align:start position:0% all developments and they're addressed at<00:07:20.360> the<00:07:20.510> time<00:07:20.870> of<00:07:21.230> the<00:07:21.380> site<00:07:21.650> or<00:07:22.010> subdivision 00:07:22.720 --> 00:07:22.730 align:start position:0% at the time of the site or subdivision 00:07:22.730 --> 00:07:25.540 align:start position:0% at the time of the site or subdivision plan<00:07:22.940> approval<00:07:23.510> in<00:07:23.830> certain<00:07:24.830> cases<00:07:25.130> the 00:07:25.540 --> 00:07:25.550 align:start position:0% plan approval in certain cases the 00:07:25.550 --> 00:07:27.640 align:start position:0% plan approval in certain cases the Planning<00:07:25.940> Director<00:07:26.030> can<00:07:26.540> waive<00:07:26.780> requirements 00:07:27.640 --> 00:07:27.650 align:start position:0% Planning Director can waive requirements 00:07:27.650 --> 00:07:29.620 align:start position:0% Planning Director can waive requirements for<00:07:27.860> connectivity<00:07:28.340> of<00:07:28.580> streets<00:07:29.060> but<00:07:29.420> that's 00:07:29.620 --> 00:07:29.630 align:start position:0% for connectivity of streets but that's 00:07:29.630 --> 00:07:34.300 align:start position:0% for connectivity of streets but that's limited<00:07:30.410> to<00:07:30.800> the<00:07:31.160> reasons<00:07:31.790> being<00:07:33.310> topographic 00:07:34.300 --> 00:07:34.310 align:start position:0% limited to the reasons being topographic 00:07:34.310 --> 00:07:36.880 align:start position:0% limited to the reasons being topographic considerations<00:07:35.090> such<00:07:35.210> if<00:07:35.570> you<00:07:35.690> have<00:07:35.870> a<00:07:35.900> stream 00:07:36.880 --> 00:07:36.890 align:start position:0% considerations such if you have a stream 00:07:36.890 --> 00:07:40.900 align:start position:0% considerations such if you have a stream buffer<00:07:37.310> or<00:07:37.340> stream<00:07:37.790> or<00:07:38.720> a<00:07:39.910> significant 00:07:40.900 --> 00:07:40.910 align:start position:0% buffer or stream or a significant 00:07:40.910 --> 00:07:43.000 align:start position:0% buffer or stream or a significant elevation<00:07:41.570> change<00:07:42.170> at<00:07:42.320> the<00:07:42.410> property<00:07:42.860> line 00:07:43.000 --> 00:07:43.010 align:start position:0% elevation change at the property line 00:07:43.010 --> 00:07:45.880 align:start position:0% elevation change at the property line that<00:07:43.280> makes<00:07:43.520> a<00:07:43.880> connection<00:07:44.540> not<00:07:45.110> feasible<00:07:45.380> and 00:07:45.880 --> 00:07:45.890 align:start position:0% that makes a connection not feasible and 00:07:45.890 --> 00:07:49.180 align:start position:0% that makes a connection not feasible and then<00:07:46.790> other<00:07:47.260> waivers<00:07:48.260> can<00:07:48.560> be<00:07:48.710> granted<00:07:49.070> by 00:07:49.180 --> 00:07:49.190 align:start position:0% then other waivers can be granted by 00:07:49.190 --> 00:07:52.450 align:start position:0% then other waivers can be granted by town<00:07:49.430> council<00:07:50.000> but<00:07:50.540> again<00:07:50.810> that<00:07:51.050> is<00:07:51.320> not<00:07:52.190> at 00:07:52.450 --> 00:07:52.460 align:start position:0% town council but again that is not at 00:07:52.460 --> 00:07:53.950 align:start position:0% town council but again that is not at the<00:07:52.580> time<00:07:52.730> of<00:07:52.910> the<00:07:52.970> rezoning<00:07:53.390> but<00:07:53.690> at<00:07:53.810> the<00:07:53.930> time 00:07:53.950 --> 00:07:53.960 align:start position:0% the time of the rezoning but at the time 00:07:53.960 --> 00:07:56.490 align:start position:0% the time of the rezoning but at the time of<00:07:54.410> the<00:07:54.890> subdivision<00:07:55.610> or<00:07:55.700> site<00:07:55.910> plan<00:07:56.180> approval 00:07:56.490 --> 00:07:56.500 align:start position:0% of the subdivision or site plan approval 00:07:56.500 --> 00:07:59.920 align:start position:0% of the subdivision or site plan approval the<00:07:57.500> one<00:07:58.340> reason<00:07:58.850> that<00:07:58.880> this<00:07:59.480> is<00:07:59.690> not 00:07:59.920 --> 00:07:59.930 align:start position:0% the one reason that this is not 00:07:59.930 --> 00:08:02.680 align:start position:0% the one reason that this is not addressed<00:08:00.800> at<00:08:01.130> the<00:08:01.430> rezoning<00:08:01.970> stage<00:08:02.420> is 00:08:02.680 --> 00:08:02.690 align:start position:0% addressed at the rezoning stage is 00:08:02.690 --> 00:08:04.750 align:start position:0% addressed at the rezoning stage is because<00:08:03.050> you<00:08:03.200> can't<00:08:03.470> have<00:08:03.560> zoning<00:08:04.010> conditions 00:08:04.750 --> 00:08:04.760 align:start position:0% because you can't have zoning conditions 00:08:04.760 --> 00:08:07.780 align:start position:0% because you can't have zoning conditions that<00:08:05.120> are<00:08:05.230> less<00:08:06.230> restrictive<00:08:07.100> than<00:08:07.310> what<00:08:07.670> the 00:08:07.780 --> 00:08:07.790 align:start position:0% that are less restrictive than what the 00:08:07.790 --> 00:08:10.660 align:start position:0% that are less restrictive than what the ordinance<00:08:08.270> requires<00:08:09.080> and<00:08:09.530> currently<00:08:10.400> the 00:08:10.660 --> 00:08:10.670 align:start position:0% ordinance requires and currently the 00:08:10.670 --> 00:08:12.800 align:start position:0% ordinance requires and currently the ordinance<00:08:11.120> does<00:08:11.330> not<00:08:11.600> really 00:08:12.800 --> 00:08:12.810 align:start position:0% ordinance does not really 00:08:12.810 --> 00:08:14.510 align:start position:0% ordinance does not really very<00:08:12.930> very<00:08:13.139> much<00:08:13.290> leeway<00:08:13.800> for<00:08:13.980> making 00:08:14.510 --> 00:08:14.520 align:start position:0% very very much leeway for making 00:08:14.520 --> 00:08:18.200 align:start position:0% very very much leeway for making exceptions<00:08:15.650> so<00:08:16.650> that<00:08:16.830> it<00:08:16.950> needs<00:08:17.190> to<00:08:17.430> go<00:08:17.639> you 00:08:18.200 --> 00:08:18.210 align:start position:0% exceptions so that it needs to go you 00:08:18.210 --> 00:08:21.350 align:start position:0% exceptions so that it needs to go you know<00:08:18.240> go<00:08:18.389> forward<00:08:19.080> to<00:08:19.290> the<00:08:19.850> the<00:08:20.850> town<00:08:21.090> council 00:08:21.350 --> 00:08:21.360 align:start position:0% know go forward to the the town council 00:08:21.360 --> 00:08:25.100 align:start position:0% know go forward to the the town council through<00:08:22.260> quasi<00:08:23.100> judicial<00:08:23.280> process<00:08:24.270> which<00:08:24.930> is 00:08:25.100 --> 00:08:25.110 align:start position:0% through quasi judicial process which is 00:08:25.110 --> 00:08:26.720 align:start position:0% through quasi judicial process which is what's<00:08:25.320> required<00:08:25.530> in<00:08:25.950> order<00:08:26.130> for<00:08:26.430> Town 00:08:26.720 --> 00:08:26.730 align:start position:0% what's required in order for Town 00:08:26.730 --> 00:08:29.870 align:start position:0% what's required in order for Town Council<00:08:26.760> to<00:08:27.480> make<00:08:27.740> decisions<00:08:28.740> or<00:08:29.250> exceptions 00:08:29.870 --> 00:08:29.880 align:start position:0% Council to make decisions or exceptions 00:08:29.880 --> 00:08:37.969 align:start position:0% Council to make decisions or exceptions at<00:08:30.180> a<00:08:30.210> site<00:08:30.630> plan<00:08:30.660> stage<00:08:34.550> the<00:08:36.919> amendment<00:08:37.919> is 00:08:37.969 --> 00:08:37.979 align:start position:0% at a site plan stage the amendment is 00:08:37.979 --> 00:08:40.279 align:start position:0% at a site plan stage the amendment is proposed<00:08:38.490> would<00:08:38.820> classify<00:08:39.289> existing 00:08:40.279 --> 00:08:40.289 align:start position:0% proposed would classify existing 00:08:40.289 --> 00:08:42.670 align:start position:0% proposed would classify existing neighborhoods<00:08:40.890> into<00:08:41.130> one<00:08:41.370> of<00:08:41.550> three<00:08:41.580> tears 00:08:42.670 --> 00:08:42.680 align:start position:0% neighborhoods into one of three tears 00:08:42.680 --> 00:08:45.290 align:start position:0% neighborhoods into one of three tears those<00:08:43.680> tears<00:08:44.039> are<00:08:44.310> based<00:08:44.550> on<00:08:44.880> when<00:08:45.180> the 00:08:45.290 --> 00:08:45.300 align:start position:0% those tears are based on when the 00:08:45.300 --> 00:08:46.880 align:start position:0% those tears are based on when the development<00:08:45.900> plan<00:08:46.020> for<00:08:46.380> the<00:08:46.440> neighborhood 00:08:46.880 --> 00:08:46.890 align:start position:0% development plan for the neighborhood 00:08:46.890 --> 00:08:48.769 align:start position:0% development plan for the neighborhood was<00:08:47.040> approved<00:08:47.490> whether<00:08:48.120> or<00:08:48.330> not<00:08:48.450> there<00:08:48.750> are 00:08:48.769 --> 00:08:48.779 align:start position:0% was approved whether or not there are 00:08:48.779 --> 00:08:50.600 align:start position:0% was approved whether or not there are street<00:08:49.290> studs<00:08:49.650> existing<00:08:50.339> in<00:08:50.460> that 00:08:50.600 --> 00:08:50.610 align:start position:0% street studs existing in that 00:08:50.610 --> 00:08:52.910 align:start position:0% street studs existing in that neighborhood<00:08:51.120> and<00:08:51.390> whether<00:08:52.320> or<00:08:52.440> not<00:08:52.560> there 00:08:52.910 --> 00:08:52.920 align:start position:0% neighborhood and whether or not there 00:08:52.920 --> 00:08:55.760 align:start position:0% neighborhood and whether or not there are<00:08:52.950> public<00:08:53.250> safety<00:08:53.850> concerns<00:08:54.560> that<00:08:55.560> are 00:08:55.760 --> 00:08:55.770 align:start position:0% are public safety concerns that are 00:08:55.770 --> 00:09:00.250 align:start position:0% are public safety concerns that are related<00:08:56.190> to<00:08:57.500> access<00:08:58.500> between<00:08:59.220> the<00:08:59.640> two 00:09:00.250 --> 00:09:00.260 align:start position:0% related to access between the two 00:09:00.260 --> 00:09:04.370 align:start position:0% related to access between the two development<00:09:01.260> the<00:09:02.070> reason<00:09:02.779> I've<00:09:03.779> had<00:09:04.080> a<00:09:04.110> couple 00:09:04.370 --> 00:09:04.380 align:start position:0% development the reason I've had a couple 00:09:04.380 --> 00:09:07.160 align:start position:0% development the reason I've had a couple of<00:09:04.680> questions<00:09:05.370> related<00:09:05.910> to<00:09:05.940> the<00:09:06.180> date<00:09:06.779> of 00:09:07.160 --> 00:09:07.170 align:start position:0% of questions related to the date of 00:09:07.170 --> 00:09:10.730 align:start position:0% of questions related to the date of january<00:09:07.710> fourteenth<00:09:08.250> 1999<00:09:09.210> the<00:09:10.200> reason<00:09:10.560> for 00:09:10.730 --> 00:09:10.740 align:start position:0% january fourteenth 1999 the reason for 00:09:10.740 --> 00:09:12.500 align:start position:0% january fourteenth 1999 the reason for that<00:09:10.770> particular<00:09:11.070> date<00:09:11.670> is<00:09:11.880> that's<00:09:12.089> when<00:09:12.390> the 00:09:12.500 --> 00:09:12.510 align:start position:0% that particular date is that's when the 00:09:12.510 --> 00:09:15.950 align:start position:0% that particular date is that's when the connectivity<00:09:13.820> requirements<00:09:14.820> were<00:09:15.060> initially 00:09:15.950 --> 00:09:15.960 align:start position:0% connectivity requirements were initially 00:09:15.960 --> 00:09:18.079 align:start position:0% connectivity requirements were initially adopted<00:09:16.290> so<00:09:16.860> all<00:09:17.040> the<00:09:17.280> subdivisions<00:09:17.550> that 00:09:18.079 --> 00:09:18.089 align:start position:0% adopted so all the subdivisions that 00:09:18.089 --> 00:09:21.170 align:start position:0% adopted so all the subdivisions that have<00:09:18.420> been<00:09:18.990> approved<00:09:19.410> since<00:09:19.800> then<00:09:20.100> have<00:09:20.640> taken 00:09:21.170 --> 00:09:21.180 align:start position:0% have been approved since then have taken 00:09:21.180 --> 00:09:23.510 align:start position:0% have been approved since then have taken our<00:09:21.510> connectivity<00:09:22.050> into<00:09:22.530> account<00:09:22.920> have<00:09:23.250> made 00:09:23.510 --> 00:09:23.520 align:start position:0% our connectivity into account have made 00:09:23.520 --> 00:09:30.790 align:start position:0% our connectivity into account have made required<00:09:24.000> stubs<00:09:24.450> to<00:09:24.660> the<00:09:24.780> property<00:09:25.260> lines 00:09:30.790 --> 00:09:30.800 align:start position:0% 00:09:30.800 --> 00:09:33.500 align:start position:0% with<00:09:31.800> the<00:09:32.100> i<00:09:32.520> won't<00:09:32.910> go<00:09:33.089> through<00:09:33.120> this<00:09:33.450> in 00:09:33.500 --> 00:09:33.510 align:start position:0% with the i won't go through this in 00:09:33.510 --> 00:09:36.050 align:start position:0% with the i won't go through this in detail<00:09:33.690> unless<00:09:34.260> we<00:09:34.560> need<00:09:34.740> to<00:09:34.800> reference<00:09:35.640> it 00:09:36.050 --> 00:09:36.060 align:start position:0% detail unless we need to reference it 00:09:36.060 --> 00:09:38.540 align:start position:0% detail unless we need to reference it but<00:09:36.240> basically<00:09:36.720> with<00:09:37.650> the<00:09:37.680> changes<00:09:38.339> that 00:09:38.540 --> 00:09:38.550 align:start position:0% but basically with the changes that 00:09:38.550 --> 00:09:41.810 align:start position:0% but basically with the changes that we're<00:09:38.730> proposing<00:09:39.710> with<00:09:40.710> the<00:09:40.950> tiered<00:09:41.610> approach 00:09:41.810 --> 00:09:41.820 align:start position:0% we're proposing with the tiered approach 00:09:41.820 --> 00:09:43.940 align:start position:0% we're proposing with the tiered approach with<00:09:42.390> with<00:09:42.750> different<00:09:43.230> neighborhoods<00:09:43.710> we're 00:09:43.940 --> 00:09:43.950 align:start position:0% with with different neighborhoods we're 00:09:43.950 --> 00:09:46.210 align:start position:0% with with different neighborhoods we're depending<00:09:44.520> on<00:09:44.520> the<00:09:44.820> tier<00:09:45.120> that<00:09:45.390> you're<00:09:45.540> in 00:09:46.210 --> 00:09:46.220 align:start position:0% depending on the tier that you're in 00:09:46.220 --> 00:09:48.640 align:start position:0% depending on the tier that you're in establishes<00:09:47.220> what<00:09:47.250> let<00:09:47.670> what<00:09:48.000> level<00:09:48.390> of 00:09:48.640 --> 00:09:48.650 align:start position:0% establishes what let what level of 00:09:48.650 --> 00:09:55.220 align:start position:0% establishes what let what level of connectivity<00:09:49.650> required<00:09:50.460> to<00:09:50.640> make<00:09:52.910> the<00:09:54.230> with 00:09:55.220 --> 00:09:55.230 align:start position:0% connectivity required to make the with 00:09:55.230 --> 00:09:58.480 align:start position:0% connectivity required to make the with the<00:09:55.580> with<00:09:56.580> setting<00:09:57.000> up<00:09:57.089> these<00:09:57.300> tears<00:09:57.720> then 00:09:58.480 --> 00:09:58.490 align:start position:0% the with setting up these tears then 00:09:58.490 --> 00:10:01.390 align:start position:0% the with setting up these tears then applicants<00:09:59.490> could<00:09:59.790> offer<00:10:00.060> zoning<00:10:00.720> conditions 00:10:01.390 --> 00:10:01.400 align:start position:0% applicants could offer zoning conditions 00:10:01.400 --> 00:10:03.800 align:start position:0% applicants could offer zoning conditions depending<00:10:02.400> on<00:10:02.910> the<00:10:03.000> tier<00:10:03.240> of<00:10:03.480> the<00:10:03.570> adjacent 00:10:03.800 --> 00:10:03.810 align:start position:0% depending on the tier of the adjacent 00:10:03.810 --> 00:10:06.710 align:start position:0% depending on the tier of the adjacent neighborhood<00:10:04.530> as<00:10:04.770> long<00:10:05.700> and<00:10:06.360> those 00:10:06.710 --> 00:10:06.720 align:start position:0% neighborhood as long and those 00:10:06.720 --> 00:10:08.840 align:start position:0% neighborhood as long and those conditions<00:10:07.200> could<00:10:07.680> include<00:10:08.040> providing<00:10:08.459> a 00:10:08.840 --> 00:10:08.850 align:start position:0% conditions could include providing a 00:10:08.850 --> 00:10:11.240 align:start position:0% conditions could include providing a full<00:10:09.060> road<00:10:09.330> connection<00:10:10.050> not<00:10:10.560> providing<00:10:11.160> a 00:10:11.240 --> 00:10:11.250 align:start position:0% full road connection not providing a 00:10:11.250 --> 00:10:14.690 align:start position:0% full road connection not providing a full<00:10:11.430> road<00:10:11.700> connection<00:10:12.300> or<00:10:13.459> providing<00:10:14.459> an 00:10:14.690 --> 00:10:14.700 align:start position:0% full road connection or providing an 00:10:14.700 --> 00:10:19.960 align:start position:0% full road connection or providing an emergency<00:10:15.480> connection<00:10:16.410> only<00:10:16.680> and<00:10:17.330> the<00:10:18.890> the 00:10:19.960 --> 00:10:19.970 align:start position:0% emergency connection only and the the 00:10:19.970 --> 00:10:22.370 align:start position:0% emergency connection only and the the condition<00:10:20.970> zoning<00:10:21.510> conditions<00:10:22.050> that<00:10:22.230> could 00:10:22.370 --> 00:10:22.380 align:start position:0% condition zoning conditions that could 00:10:22.380 --> 00:10:25.510 align:start position:0% condition zoning conditions that could be<00:10:22.560> accepted<00:10:23.250> depend<00:10:23.970> on<00:10:24.270> the<00:10:24.780> tier<00:10:25.050> of<00:10:25.200> the 00:10:25.510 --> 00:10:25.520 align:start position:0% be accepted depend on the tier of the 00:10:25.520 --> 00:10:28.050 align:start position:0% be accepted depend on the tier of the in<00:10:25.970> the<00:10:26.060> specific<00:10:26.600> conditions<00:10:27.200> again 00:10:28.050 --> 00:10:28.060 align:start position:0% in the specific conditions again 00:10:28.060 --> 00:10:31.300 align:start position:0% in the specific conditions again ensuring<00:10:29.060> that<00:10:29.090> no<00:10:30.050> conditions<00:10:30.710> are<00:10:30.860> offered 00:10:31.300 --> 00:10:31.310 align:start position:0% ensuring that no conditions are offered 00:10:31.310 --> 00:10:34.300 align:start position:0% ensuring that no conditions are offered that<00:10:31.550> that<00:10:32.300> are<00:10:32.570> less<00:10:32.870> restrictive<00:10:33.620> than<00:10:33.830> what 00:10:34.300 --> 00:10:34.310 align:start position:0% that that are less restrictive than what 00:10:34.310 --> 00:10:37.900 align:start position:0% that that are less restrictive than what the<00:10:34.460> underlying<00:10:35.560> zoning<00:10:36.560> allows<00:10:36.770> and<00:10:37.700> what's 00:10:37.900 --> 00:10:37.910 align:start position:0% the underlying zoning allows and what's 00:10:37.910 --> 00:10:47.140 align:start position:0% the underlying zoning allows and what's applicable<00:10:38.270> to<00:10:38.780> that<00:10:39.560> particular<00:10:39.830> tier<00:10:46.150> the 00:10:47.140 --> 00:10:47.150 align:start position:0% applicable to that particular tier the 00:10:47.150 --> 00:10:52.380 align:start position:0% applicable to that particular tier the second<00:10:47.630> item<00:10:47.840> item<00:10:48.740> C<00:10:49.070> is<00:10:50.350> related<00:10:51.350> two 00:10:52.380 --> 00:10:52.390 align:start position:0% second item item C is related two 00:10:52.390 --> 00:10:54.700 align:start position:0% second item item C is related two dimensional<00:10:53.390> standards<00:10:53.870> for<00:10:54.080> low<00:10:54.230> density 00:10:54.700 --> 00:10:54.710 align:start position:0% dimensional standards for low density 00:10:54.710 --> 00:10:57.040 align:start position:0% dimensional standards for low density residential<00:10:55.160> development<00:10:55.790> this<00:10:56.660> amendment 00:10:57.040 --> 00:10:57.050 align:start position:0% residential development this amendment 00:10:57.050 --> 00:10:59.710 align:start position:0% residential development this amendment was<00:10:57.410> prepared<00:10:58.340> in<00:10:58.550> response<00:10:59.060> to<00:10:59.300> concerns 00:10:59.710 --> 00:10:59.720 align:start position:0% was prepared in response to concerns 00:10:59.720 --> 00:11:02.410 align:start position:0% was prepared in response to concerns that<00:10:59.990> some<00:11:00.350> new<00:11:00.620> development<00:11:01.310> in<00:11:01.550> areas<00:11:01.940> that 00:11:02.410 --> 00:11:02.420 align:start position:0% that some new development in areas that 00:11:02.420 --> 00:11:04.780 align:start position:0% that some new development in areas that are<00:11:02.540> designated<00:11:03.230> in<00:11:03.350> the<00:11:03.410> land<00:11:03.710> use<00:11:03.950> plan<00:11:04.280> for 00:11:04.780 --> 00:11:04.790 align:start position:0% are designated in the land use plan for 00:11:04.790 --> 00:11:06.490 align:start position:0% are designated in the land use plan for low<00:11:04.940> density<00:11:05.420> development<00:11:05.690> or<00:11:06.110> very<00:11:06.320> low 00:11:06.490 --> 00:11:06.500 align:start position:0% low density development or very low 00:11:06.500 --> 00:11:10.540 align:start position:0% low density development or very low density<00:11:06.530> development<00:11:08.230> often<00:11:09.230> failed<00:11:10.070> to<00:11:10.310> meet 00:11:10.540 --> 00:11:10.550 align:start position:0% density development often failed to meet 00:11:10.550 --> 00:11:13.990 align:start position:0% density development often failed to meet expectations<00:11:11.120> of<00:11:12.050> citizens<00:11:12.680> and<00:11:13.000> council 00:11:13.990 --> 00:11:14.000 align:start position:0% expectations of citizens and council 00:11:14.000 --> 00:11:16.360 align:start position:0% expectations of citizens and council members<00:11:14.300> and<00:11:14.480> board<00:11:14.660> members<00:11:15.020> related<00:11:15.680> to<00:11:15.890> lot 00:11:16.360 --> 00:11:16.370 align:start position:0% members and board members related to lot 00:11:16.370 --> 00:11:19.530 align:start position:0% members and board members related to lot size<00:11:16.730> and<00:11:16.760> other<00:11:17.240> dimensional<00:11:17.870> requirements 00:11:19.530 --> 00:11:19.540 align:start position:0% size and other dimensional requirements 00:11:19.540 --> 00:11:23.920 align:start position:0% size and other dimensional requirements this<00:11:20.540> issue<00:11:20.750> was<00:11:21.050> also<00:11:21.560> discussed<00:11:22.220> at<00:11:22.780> the<00:11:23.780> to 00:11:23.920 --> 00:11:23.930 align:start position:0% this issue was also discussed at the to 00:11:23.930 --> 00:11:25.780 align:start position:0% this issue was also discussed at the to council<00:11:24.410> work<00:11:24.560> sessions<00:11:25.100> in<00:11:25.280> the<00:11:25.310> two<00:11:25.550> prior 00:11:25.780 --> 00:11:25.790 align:start position:0% council work sessions in the two prior 00:11:25.790 --> 00:11:27.610 align:start position:0% council work sessions in the two prior public<00:11:26.270> hearings<00:11:26.660> so<00:11:26.810> this<00:11:26.990> has<00:11:27.140> had<00:11:27.380> a 00:11:27.610 --> 00:11:27.620 align:start position:0% public hearings so this has had a 00:11:27.620 --> 00:11:32.230 align:start position:0% public hearings so this has had a lengthy<00:11:28.630> vetting<00:11:29.630> and<00:11:30.640> revision<00:11:31.640> process 00:11:32.230 --> 00:11:32.240 align:start position:0% lengthy vetting and revision process 00:11:32.240 --> 00:11:40.690 align:start position:0% lengthy vetting and revision process along<00:11:32.810> the<00:11:32.990> way<00:11:33.110> as<00:11:33.260> well<00:11:39.100> based<00:11:40.100> on<00:11:40.370> feedback 00:11:40.690 --> 00:11:40.700 align:start position:0% along the way as well based on feedback 00:11:40.700 --> 00:11:42.730 align:start position:0% along the way as well based on feedback in<00:11:41.180> Council<00:11:41.630> Direction<00:11:42.110> received<00:11:42.530> the 00:11:42.730 --> 00:11:42.740 align:start position:0% in Council Direction received the 00:11:42.740 --> 00:11:45.100 align:start position:0% in Council Direction received the amendment<00:11:43.220> is<00:11:43.310> currently<00:11:43.730> proposed<00:11:44.300> with 00:11:45.100 --> 00:11:45.110 align:start position:0% amendment is currently proposed with 00:11:45.110 --> 00:11:48.520 align:start position:0% amendment is currently proposed with prohibit<00:11:45.860> new<00:11:46.330> TR<00:11:47.330> which<00:11:47.660> is<00:11:47.840> transitional 00:11:48.520 --> 00:11:48.530 align:start position:0% prohibit new TR which is transitional 00:11:48.530 --> 00:11:51.250 align:start position:0% prohibit new TR which is transitional residential<00:11:49.160> and<00:11:49.390> TR<00:11:50.390> conditional<00:11:51.050> use 00:11:51.250 --> 00:11:51.260 align:start position:0% residential and TR conditional use 00:11:51.260 --> 00:11:52.930 align:start position:0% residential and TR conditional use districts<00:11:51.890> where<00:11:52.280> the<00:11:52.460> plan<00:11:52.700> designation 00:11:52.930 --> 00:11:52.940 align:start position:0% districts where the plan designation 00:11:52.940 --> 00:11:55.260 align:start position:0% districts where the plan designation calls<00:11:53.780> for<00:11:54.140> low<00:11:54.320> or<00:11:54.620> very<00:11:54.650> low<00:11:55.070> density 00:11:55.260 --> 00:11:55.270 align:start position:0% calls for low or very low density 00:11:55.270 --> 00:11:58.830 align:start position:0% calls for low or very low density residential<00:11:56.270> development<00:11:56.960> and<00:11:57.580> would<00:11:58.580> also 00:11:58.830 --> 00:11:58.840 align:start position:0% residential development and would also 00:11:58.840 --> 00:12:03.190 align:start position:0% residential development and would also specify<00:11:59.840> which<00:12:00.320> designations<00:12:02.200> plan 00:12:03.190 --> 00:12:03.200 align:start position:0% specify which designations plan 00:12:03.200 --> 00:12:05.680 align:start position:0% specify which designations plan designations<00:12:03.980> would<00:12:04.190> be<00:12:04.370> required<00:12:04.670> in<00:12:05.300> order 00:12:05.680 --> 00:12:05.690 align:start position:0% designations would be required in order 00:12:05.690 --> 00:12:08.650 align:start position:0% designations would be required in order to<00:12:06.140> request<00:12:06.890> rezoning<00:12:07.700> to<00:12:08.300> certain 00:12:08.650 --> 00:12:08.660 align:start position:0% to request rezoning to certain 00:12:08.660 --> 00:12:10.630 align:start position:0% to request rezoning to certain residential<00:12:09.230> districts<00:12:09.740> so<00:12:09.830> it<00:12:09.980> tries<00:12:10.250> in<00:12:10.610> the 00:12:10.630 --> 00:12:10.640 align:start position:0% residential districts so it tries in the 00:12:10.640 --> 00:12:12.970 align:start position:0% residential districts so it tries in the ordinance<00:12:11.240> to<00:12:11.870> establish<00:12:12.470> a<00:12:12.500> closer 00:12:12.970 --> 00:12:12.980 align:start position:0% ordinance to establish a closer 00:12:12.980 --> 00:12:15.790 align:start position:0% ordinance to establish a closer relationship<00:12:13.360> between<00:12:14.360> the<00:12:14.930> land<00:12:15.170> use<00:12:15.440> plan 00:12:15.790 --> 00:12:15.800 align:start position:0% relationship between the land use plan 00:12:15.800 --> 00:12:19.240 align:start position:0% relationship between the land use plan and<00:12:16.600> some<00:12:17.600> of<00:12:17.630> the<00:12:17.870> key<00:12:18.080> zoning<00:12:18.590> districts<00:12:19.070> and 00:12:19.240 --> 00:12:19.250 align:start position:0% and some of the key zoning districts and 00:12:19.250 --> 00:12:21.940 align:start position:0% and some of the key zoning districts and when<00:12:19.490> you<00:12:20.060> would<00:12:20.210> be<00:12:20.360> eligible<00:12:20.990> to<00:12:21.020> even<00:12:21.680> make 00:12:21.940 --> 00:12:21.950 align:start position:0% when you would be eligible to even make 00:12:21.950 --> 00:12:28.210 align:start position:0% when you would be eligible to even make a<00:12:22.010> request<00:12:22.400> for<00:12:22.760> those<00:12:26.230> this<00:12:27.230> table<00:12:27.710> shows 00:12:28.210 --> 00:12:28.220 align:start position:0% a request for those this table shows 00:12:28.220 --> 00:12:32.830 align:start position:0% a request for those this table shows that<00:12:28.820> relationship<00:12:30.160> for<00:12:31.160> example<00:12:31.730> you<00:12:32.300> can 00:12:32.830 --> 00:12:32.840 align:start position:0% that relationship for example you can 00:12:32.840 --> 00:12:36.810 align:start position:0% that relationship for example you can see<00:12:33.080> the<00:12:33.290> in<00:12:33.530> the<00:12:33.680> RR<00:12:33.860> 12<00:12:34.730> district<00:12:35.330> could<00:12:35.960> be 00:12:36.810 --> 00:12:36.820 align:start position:0% see the in the RR 12 district could be 00:12:36.820 --> 00:12:39.580 align:start position:0% see the in the RR 12 district could be requested<00:12:37.820> in<00:12:38.090> a<00:12:38.270> V<00:12:38.510> LDR<00:12:39.050> very<00:12:39.380> low 00:12:39.580 --> 00:12:39.590 align:start position:0% requested in a V LDR very low 00:12:39.590 --> 00:12:41.950 align:start position:0% requested in a V LDR very low density<00:12:40.010> residential<00:12:40.490> the<00:12:41.210> low<00:12:41.390> density<00:12:41.930> or 00:12:41.950 --> 00:12:41.960 align:start position:0% density residential the low density or 00:12:41.960 --> 00:12:46.620 align:start position:0% density residential the low density or the<00:12:42.200> medium<00:12:42.530> density<00:12:42.970> residential<00:12:44.650> category 00:12:46.620 --> 00:12:46.630 align:start position:0% the medium density residential category 00:12:46.630 --> 00:12:52.420 align:start position:0% the medium density residential category r8<00:12:47.630> could<00:12:48.350> also<00:12:48.560> be<00:12:49.150> requested<00:12:50.150> in<00:12:50.950> those<00:12:51.950> same 00:12:52.420 --> 00:12:52.430 align:start position:0% r8 could also be requested in those same 00:12:52.430 --> 00:12:55.600 align:start position:0% r8 could also be requested in those same districts<00:12:53.120> and<00:12:53.330> also<00:12:53.750> in<00:12:53.990> the<00:12:54.470> HDR<00:12:55.160> or<00:12:55.340> the 00:12:55.600 --> 00:12:55.610 align:start position:0% districts and also in the HDR or the 00:12:55.610 --> 00:13:00.090 align:start position:0% districts and also in the HDR or the high<00:12:55.790> density<00:12:56.330> area<00:12:56.870> so<00:12:57.230> in<00:12:57.500> this<00:12:58.130> example<00:12:58.750> in 00:13:00.090 --> 00:13:00.100 align:start position:0% high density area so in this example in 00:13:00.100 --> 00:13:04.570 align:start position:0% high density area so in this example in a<00:13:01.180> area<00:13:02.180> where<00:13:02.750> the<00:13:03.620> plan<00:13:04.010> calls<00:13:04.400> for 00:13:04.570 --> 00:13:04.580 align:start position:0% a area where the plan calls for 00:13:04.580 --> 00:13:06.400 align:start position:0% a area where the plan calls for high-density<00:13:05.090> residential<00:13:05.870> we<00:13:06.170> would<00:13:06.290> be 00:13:06.400 --> 00:13:06.410 align:start position:0% high-density residential we would be 00:13:06.410 --> 00:13:11.140 align:start position:0% high-density residential we would be looking<00:13:06.620> for<00:13:08.170> you<00:13:09.170> know<00:13:09.320> the<00:13:09.710> r12<00:13:10.400> would<00:13:10.940> not 00:13:11.140 --> 00:13:11.150 align:start position:0% looking for you know the r12 would not 00:13:11.150 --> 00:13:12.970 align:start position:0% looking for you know the r12 would not be<00:13:11.390> allowed<00:13:11.720> because<00:13:12.020> the<00:13:12.320> density<00:13:12.500> there 00:13:12.970 --> 00:13:12.980 align:start position:0% be allowed because the density there 00:13:12.980 --> 00:13:18.040 align:start position:0% be allowed because the density there would<00:13:13.250> be<00:13:14.080> not<00:13:15.080> not<00:13:15.890> great<00:13:16.400> enough<00:13:16.670> to<00:13:17.050> meet 00:13:18.040 --> 00:13:18.050 align:start position:0% would be not not great enough to meet 00:13:18.050 --> 00:13:22.210 align:start position:0% would be not not great enough to meet the<00:13:18.080> requirement<00:13:18.650> for<00:13:18.680> the<00:13:19.100> high<00:13:19.310> density<00:13:21.220> if 00:13:22.210 --> 00:13:22.220 align:start position:0% the requirement for the high density if 00:13:22.220 --> 00:13:24.460 align:start position:0% the requirement for the high density if you<00:13:22.550> look<00:13:22.760> to<00:13:22.940> the<00:13:22.970> column<00:13:23.450> for<00:13:23.690> the<00:13:23.780> TR<00:13:24.170> the 00:13:24.460 --> 00:13:24.470 align:start position:0% you look to the column for the TR the 00:13:24.470 --> 00:13:26.350 align:start position:0% you look to the column for the TR the transitional<00:13:25.070> residential<00:13:25.670> district<00:13:26.120> here 00:13:26.350 --> 00:13:26.360 align:start position:0% transitional residential district here 00:13:26.360 --> 00:13:29.080 align:start position:0% transitional residential district here you'll<00:13:26.540> see<00:13:26.840> that<00:13:27.110> the<00:13:27.410> the<00:13:28.040> TR<00:13:28.460> district 00:13:29.080 --> 00:13:29.090 align:start position:0% you'll see that the the TR district 00:13:29.090 --> 00:13:31.720 align:start position:0% you'll see that the the TR district which<00:13:29.330> has<00:13:29.360> the<00:13:29.750> smallest<00:13:30.020> lot<00:13:30.500> sizes<00:13:31.130> the 00:13:31.720 --> 00:13:31.730 align:start position:0% which has the smallest lot sizes the 00:13:31.730 --> 00:13:32.950 align:start position:0% which has the smallest lot sizes the smallest<00:13:32.240> dimensional<00:13:32.840> requirements 00:13:32.950 --> 00:13:32.960 align:start position:0% smallest dimensional requirements 00:13:32.960 --> 00:13:36.490 align:start position:0% smallest dimensional requirements setbacks<00:13:34.600> and<00:13:35.600> allows<00:13:35.930> the<00:13:36.170> highest 00:13:36.490 --> 00:13:36.500 align:start position:0% setbacks and allows the highest 00:13:36.500 --> 00:13:40.120 align:start position:0% setbacks and allows the highest densities<00:13:37.040> would<00:13:37.670> not<00:13:37.910> be<00:13:38.300> a<00:13:39.070> district<00:13:40.070> that 00:13:40.120 --> 00:13:40.130 align:start position:0% densities would not be a district that 00:13:40.130 --> 00:13:46.120 align:start position:0% densities would not be a district that you<00:13:40.370> could<00:13:42.820> request<00:13:43.820> if<00:13:44.360> you<00:13:44.810> if<00:13:45.110> your<00:13:45.560> plan 00:13:46.120 --> 00:13:46.130 align:start position:0% you could request if you if your plan 00:13:46.130 --> 00:13:48.400 align:start position:0% you could request if you if your plan designation<00:13:46.430> called<00:13:47.360> for<00:13:47.720> the<00:13:47.870> lower<00:13:48.050> very 00:13:48.400 --> 00:13:48.410 align:start position:0% designation called for the lower very 00:13:48.410 --> 00:13:51.100 align:start position:0% designation called for the lower very low<00:13:48.590> density<00:13:48.640> development<00:13:49.640> so<00:13:50.570> it's<00:13:50.780> just<00:13:50.990> a 00:13:51.100 --> 00:13:51.110 align:start position:0% low density development so it's just a 00:13:51.110 --> 00:13:53.350 align:start position:0% low density development so it's just a way<00:13:51.260> to<00:13:51.290> try<00:13:51.650> to<00:13:51.680> to<00:13:51.980> have<00:13:52.850> that<00:13:53.090> better 00:13:53.350 --> 00:13:53.360 align:start position:0% way to try to to have that better 00:13:53.360 --> 00:13:56.620 align:start position:0% way to try to to have that better relationship<00:13:54.110> to<00:13:54.380> keep<00:13:54.620> the<00:13:55.040> the<00:13:55.640> densities 00:13:56.620 --> 00:13:56.630 align:start position:0% relationship to keep the the densities 00:13:56.630 --> 00:13:59.530 align:start position:0% relationship to keep the the densities from<00:13:57.260> the<00:13:57.410> zoning<00:13:57.830> and<00:13:57.950> the<00:13:58.040> densities<00:13:58.610> or<00:13:59.330> the 00:13:59.530 --> 00:13:59.540 align:start position:0% from the zoning and the densities or the 00:13:59.540 --> 00:14:01.900 align:start position:0% from the zoning and the densities or the lot<00:13:59.750> size<00:14:00.020> is<00:14:00.050> related<00:14:00.710> with<00:14:00.740> the<00:14:00.890> land<00:14:01.670> use 00:14:01.900 --> 00:14:01.910 align:start position:0% lot size is related with the land use 00:14:01.910 --> 00:14:07.990 align:start position:0% lot size is related with the land use plan<00:14:02.210> on<00:14:02.570> a<00:14:02.630> little<00:14:03.350> closer<00:14:03.680> relationship<00:14:07.000> and 00:14:07.990 --> 00:14:08.000 align:start position:0% plan on a little closer relationship and 00:14:08.000 --> 00:14:10.090 align:start position:0% plan on a little closer relationship and that<00:14:08.030> concludes<00:14:08.630> staffs<00:14:09.230> comments<00:14:09.830> it<00:14:09.980> will 00:14:10.090 --> 00:14:10.100 align:start position:0% that concludes staffs comments it will 00:14:10.100 --> 00:14:15.040 align:start position:0% that concludes staffs comments it will be<00:14:10.220> glad<00:14:11.180> to<00:14:11.240> answer<00:14:11.540> any<00:14:11.930> questions<00:14:14.050> thank 00:14:15.040 --> 00:14:15.050 align:start position:0% be glad to answer any questions thank 00:14:15.050 --> 00:14:17.610 align:start position:0% be glad to answer any questions thank you<00:14:15.760> let's<00:14:16.760> take<00:14:16.970> the<00:14:17.090> first<00:14:17.300> one 00:14:17.610 --> 00:14:17.620 align:start position:0% you let's take the first one 00:14:17.620 --> 00:14:21.860 align:start position:0% you let's take the first one connectivity 00:14:21.860 --> 00:14:21.870 align:start position:0% 00:14:21.870 --> 00:14:25.940 align:start position:0% so<00:14:22.870> if<00:14:23.590> I<00:14:23.770> understand<00:14:24.370> this<00:14:24.520> correctly<00:14:24.580> a 00:14:25.940 --> 00:14:25.950 align:start position:0% so if I understand this correctly a 00:14:25.950 --> 00:14:30.120 align:start position:0% so if I understand this correctly a neighborhood<00:14:26.950> approved<00:14:27.370> before<00:14:27.750> 1999<00:14:29.130> could 00:14:30.120 --> 00:14:30.130 align:start position:0% neighborhood approved before 1999 could 00:14:30.130 --> 00:14:36.090 align:start position:0% neighborhood approved before 1999 could be<00:14:30.340> at<00:14:30.460> tier<00:14:30.790> 1<00:14:32.370> if<00:14:33.370> a<00:14:34.150> public<00:14:34.660> safety<00:14:35.170> issue<00:14:35.500> is 00:14:36.090 --> 00:14:36.100 align:start position:0% be at tier 1 if a public safety issue is 00:14:36.100 --> 00:14:39.510 align:start position:0% be at tier 1 if a public safety issue is identified<00:14:36.730> as<00:14:37.090> that<00:14:37.590> or<00:14:38.590> is<00:14:38.950> our 00:14:39.510 --> 00:14:39.520 align:start position:0% identified as that or is our 00:14:39.520 --> 00:14:41.420 align:start position:0% identified as that or is our neighborhoods<00:14:40.240> that<00:14:40.690> were<00:14:40.750> built<00:14:41.140> before 00:14:41.420 --> 00:14:41.430 align:start position:0% neighborhoods that were built before 00:14:41.430 --> 00:14:45.660 align:start position:0% neighborhoods that were built before 1999<00:14:42.430> or<00:14:43.120> in<00:14:43.480> the<00:14:43.750> were<00:14:44.470> built<00:14:44.920> outside<00:14:45.190> of 00:14:45.660 --> 00:14:45.670 align:start position:0% 1999 or in the were built outside of 00:14:45.670 --> 00:14:49.110 align:start position:0% 1999 or in the were built outside of carry<00:14:46.030> are<00:14:46.300> they<00:14:46.600> always<00:14:47.370> they<00:14:48.370> never<00:14:48.730> appear 00:14:49.110 --> 00:14:49.120 align:start position:0% carry are they always they never appear 00:14:49.120 --> 00:14:52.140 align:start position:0% carry are they always they never appear one<00:14:49.950> there<00:14:50.950> it<00:14:51.340> looked<00:14:51.580> like<00:14:51.700> there<00:14:51.880> were<00:14:51.970> some 00:14:52.140 --> 00:14:52.150 align:start position:0% one there it looked like there were some 00:14:52.150 --> 00:14:53.490 align:start position:0% one there it looked like there were some conditions<00:14:52.630> here<00:14:52.900> that<00:14:53.050> you<00:14:53.140> had<00:14:53.260> to<00:14:53.380> meet 00:14:53.490 --> 00:14:53.500 align:start position:0% conditions here that you had to meet 00:14:53.500 --> 00:14:55.410 align:start position:0% conditions here that you had to meet certain<00:14:53.740> criteria<00:14:54.010> and<00:14:54.670> one<00:14:54.790> of<00:14:54.940> them<00:14:55.060> was 00:14:55.410 --> 00:14:55.420 align:start position:0% certain criteria and one of them was 00:14:55.420 --> 00:14:59.460 align:start position:0% certain criteria and one of them was that<00:14:55.570> there<00:14:55.750> was<00:14:55.900> no<00:14:57.060> public<00:14:58.060> safety<00:14:58.900> issues 00:14:59.460 --> 00:14:59.470 align:start position:0% that there was no public safety issues 00:14:59.470 --> 00:15:01.320 align:start position:0% that there was no public safety issues that<00:14:59.800> would<00:14:59.980> be<00:15:00.130> raised<00:15:00.430> and<00:15:00.910> the<00:15:00.970> question 00:15:01.320 --> 00:15:01.330 align:start position:0% that would be raised and the question 00:15:01.330 --> 00:15:03.240 align:start position:0% that would be raised and the question and<00:15:01.420> my<00:15:01.570> question<00:15:01.630> is<00:15:02.140> who<00:15:02.590> gets<00:15:02.860> to<00:15:03.130> decide 00:15:03.240 --> 00:15:03.250 align:start position:0% and my question is who gets to decide 00:15:03.250 --> 00:15:07.560 align:start position:0% and my question is who gets to decide that<00:15:03.810> and<00:15:04.810> could<00:15:05.500> you<00:15:05.830> know<00:15:06.160> say<00:15:06.430> an<00:15:06.910> older 00:15:07.560 --> 00:15:07.570 align:start position:0% that and could you know say an older 00:15:07.570 --> 00:15:09.330 align:start position:0% that and could you know say an older neighborhood<00:15:07.710> turn<00:15:08.710> into<00:15:09.010> a<00:15:09.040> Tier<00:15:09.310> one 00:15:09.330 --> 00:15:09.340 align:start position:0% neighborhood turn into a Tier one 00:15:09.340 --> 00:15:11.190 align:start position:0% neighborhood turn into a Tier one because<00:15:09.910> somebody<00:15:10.210> says<00:15:10.240> there's<00:15:10.960> going<00:15:11.140> to 00:15:11.190 --> 00:15:11.200 align:start position:0% because somebody says there's going to 00:15:11.200 --> 00:15:14.130 align:start position:0% because somebody says there's going to be<00:15:11.230> a<00:15:11.320> public<00:15:11.680> safety<00:15:11.890> issue<00:15:12.390> well<00:15:13.390> a<00:15:13.420> Tier<00:15:14.110> one 00:15:14.130 --> 00:15:14.140 align:start position:0% be a public safety issue well a Tier one 00:15:14.140 --> 00:15:19.290 align:start position:0% be a public safety issue well a Tier one neighborhood<00:15:14.980> is<00:15:15.130> basically<00:15:18.270> what<00:15:19.270> a 00:15:19.290 --> 00:15:19.300 align:start position:0% neighborhood is basically what a 00:15:19.300 --> 00:15:22.020 align:start position:0% neighborhood is basically what a neighborhood<00:15:20.230> that's<00:15:20.260> that<00:15:21.160> doesn't<00:15:21.790> fall 00:15:22.020 --> 00:15:22.030 align:start position:0% neighborhood that's that doesn't fall 00:15:22.030 --> 00:15:24.960 align:start position:0% neighborhood that's that doesn't fall into<00:15:22.060> either<00:15:22.570> a<00:15:22.750> tier<00:15:23.170> 2<00:15:23.380> or<00:15:23.590> tier<00:15:23.800> 3<00:15:24.100> and<00:15:24.370> in 00:15:24.960 --> 00:15:24.970 align:start position:0% into either a tier 2 or tier 3 and in 00:15:24.970 --> 00:15:28.020 align:start position:0% into either a tier 2 or tier 3 and in order<00:15:25.240> to<00:15:25.390> be<00:15:25.870> a<00:15:26.140> tier<00:15:26.620> 2<00:15:26.830> tier<00:15:26.860> 3<00:15:27.610> it<00:15:27.880> would 00:15:28.020 --> 00:15:28.030 align:start position:0% order to be a tier 2 tier 3 it would 00:15:28.030 --> 00:15:30.960 align:start position:0% order to be a tier 2 tier 3 it would have<00:15:28.150> had<00:15:28.390> to<00:15:28.600> have<00:15:28.660> been<00:15:28.780> approved<00:15:29.350> prior<00:15:29.970> to 00:15:30.960 --> 00:15:30.970 align:start position:0% have had to have been approved prior to 00:15:30.970 --> 00:15:32.970 align:start position:0% have had to have been approved prior to nineteen<00:15:31.750> ninety<00:15:31.990> nine<00:15:32.020> before<00:15:32.740> the 00:15:32.970 --> 00:15:32.980 align:start position:0% nineteen ninety nine before the 00:15:32.980 --> 00:15:35.250 align:start position:0% nineteen ninety nine before the connectivity<00:15:33.610> ordinance<00:15:34.030> so<00:15:34.600> all<00:15:34.900> of<00:15:34.930> the 00:15:35.250 --> 00:15:35.260 align:start position:0% connectivity ordinance so all of the 00:15:35.260 --> 00:15:37.140 align:start position:0% connectivity ordinance so all of the newer<00:15:35.500> neighborhoods<00:15:36.220> I<00:15:36.550> mean<00:15:36.970> any 00:15:37.140 --> 00:15:37.150 align:start position:0% newer neighborhoods I mean any 00:15:37.150 --> 00:15:39.530 align:start position:0% newer neighborhoods I mean any neighborhood<00:15:37.570> that<00:15:37.900> was<00:15:38.080> approved<00:15:38.410> after 00:15:39.530 --> 00:15:39.540 align:start position:0% neighborhood that was approved after 00:15:39.540 --> 00:15:42.630 align:start position:0% neighborhood that was approved after that<00:15:40.540> january<00:15:41.110> fourteenth<00:15:41.650> date<00:15:41.980> would 00:15:42.630 --> 00:15:42.640 align:start position:0% that january fourteenth date would 00:15:42.640 --> 00:15:45.180 align:start position:0% that january fourteenth date would automatically<00:15:43.360> be<00:15:43.810> classified<00:15:44.680> as<00:15:44.710> a<00:15:44.890> Tier 00:15:45.180 --> 00:15:45.190 align:start position:0% automatically be classified as a Tier 00:15:45.190 --> 00:15:48.060 align:start position:0% automatically be classified as a Tier one<00:15:45.270> because<00:15:46.270> it<00:15:46.780> doesn't<00:15:47.320> fall<00:15:47.500> into<00:15:47.530> a<00:15:47.800> tier 00:15:48.060 --> 00:15:48.070 align:start position:0% one because it doesn't fall into a tier 00:15:48.070 --> 00:15:51.930 align:start position:0% one because it doesn't fall into a tier two<00:15:48.280> or<00:15:48.430> tier<00:15:48.700> three<00:15:49.740> once<00:15:50.740> you're<00:15:51.070> in<00:15:51.310> the 00:15:51.930 --> 00:15:51.940 align:start position:0% two or tier three once you're in the 00:15:51.940 --> 00:15:56.700 align:start position:0% two or tier three once you're in the tier<00:15:52.330> two<00:15:52.690> or<00:15:52.930> three<00:15:53.230> category<00:15:54.420> if<00:15:55.420> you're<00:15:56.380> in 00:15:56.700 --> 00:15:56.710 align:start position:0% tier two or three category if you're in 00:15:56.710 --> 00:15:59.160 align:start position:0% tier two or three category if you're in either<00:15:57.490> tier<00:15:57.880> two<00:15:58.090> or<00:15:58.330> tier<00:15:58.540> three<00:15:58.870> then 00:15:59.160 --> 00:15:59.170 align:start position:0% either tier two or tier three then 00:15:59.170 --> 00:16:00.810 align:start position:0% either tier two or tier three then you're<00:15:59.380> always<00:15:59.770> required<00:16:00.280> to<00:16:00.460> provide 00:16:00.810 --> 00:16:00.820 align:start position:0% you're always required to provide 00:16:00.820 --> 00:16:03.390 align:start position:0% you're always required to provide pedestrian<00:16:01.660> bicycle<00:16:02.290> and<00:16:02.920> utility 00:16:03.390 --> 00:16:03.400 align:start position:0% pedestrian bicycle and utility 00:16:03.400 --> 00:16:08.040 align:start position:0% pedestrian bicycle and utility connections<00:16:03.970> and<00:16:04.380> then<00:16:05.380> whether<00:16:06.190> or<00:16:06.520> not<00:16:07.050> you 00:16:08.040 --> 00:16:08.050 align:start position:0% connections and then whether or not you 00:16:08.050 --> 00:16:12.330 align:start position:0% connections and then whether or not you provide<00:16:10.470> whether<00:16:11.470> or<00:16:11.650> not<00:16:11.770> you<00:16:12.010> have<00:16:12.190> to 00:16:12.330 --> 00:16:12.340 align:start position:0% provide whether or not you have to 00:16:12.340 --> 00:16:15.120 align:start position:0% provide whether or not you have to provide<00:16:12.700> a<00:16:12.760> road<00:16:13.210> connection<00:16:13.960> depends<00:16:14.830> on<00:16:14.980> if 00:16:15.120 --> 00:16:15.130 align:start position:0% provide a road connection depends on if 00:16:15.130 --> 00:16:20.010 align:start position:0% provide a road connection depends on if their<00:16:15.310> safety<00:16:15.730> issues<00:16:16.360> if<00:16:16.600> there<00:16:17.470> are<00:16:17.680> no<00:16:19.020> if 00:16:20.010 --> 00:16:20.020 align:start position:0% their safety issues if there are no if 00:16:20.020 --> 00:16:21.690 align:start position:0% their safety issues if there are no if it's<00:16:20.320> not<00:16:20.530> if<00:16:20.770> it's<00:16:20.890> determined<00:16:21.130> and<00:16:21.550> this 00:16:21.690 --> 00:16:21.700 align:start position:0% it's not if it's determined and this 00:16:21.700 --> 00:16:23.460 align:start position:0% it's not if it's determined and this would<00:16:21.880> be<00:16:21.910> with<00:16:22.210> input<00:16:22.630> from<00:16:22.660> the<00:16:23.170> fire 00:16:23.460 --> 00:16:23.470 align:start position:0% would be with input from the fire 00:16:23.470 --> 00:16:25.520 align:start position:0% would be with input from the fire department<00:16:24.070> and<00:16:24.160> Police<00:16:24.400> Department<00:16:25.030> and 00:16:25.520 --> 00:16:25.530 align:start position:0% department and Police Department and 00:16:25.530 --> 00:16:30.830 align:start position:0% department and Police Department and some<00:16:26.530> judgment<00:16:27.160> in<00:16:27.940> looking<00:16:28.900> at<00:16:29.080> the<00:16:29.370> overall 00:16:30.830 --> 00:16:30.840 align:start position:0% some judgment in looking at the overall 00:16:30.840 --> 00:16:33.850 align:start position:0% some judgment in looking at the overall interaction<00:16:31.840> of<00:16:32.500> the<00:16:32.830> proposed 00:16:33.850 --> 00:16:33.860 align:start position:0% interaction of the proposed 00:16:33.860 --> 00:16:35.920 align:start position:0% interaction of the proposed existing<00:16:34.370> developments<00:16:34.940> if<00:16:35.089> it<00:16:35.720> was 00:16:35.920 --> 00:16:35.930 align:start position:0% existing developments if it was 00:16:35.930 --> 00:16:39.250 align:start position:0% existing developments if it was determined<00:16:36.290> that<00:16:36.589> a<00:16:36.769> a<00:16:37.240> road<00:16:38.240> connection<00:16:39.019> of 00:16:39.250 --> 00:16:39.260 align:start position:0% determined that a a road connection of 00:16:39.260 --> 00:16:41.319 align:start position:0% determined that a a road connection of some<00:16:39.500> sort<00:16:39.829> was<00:16:40.010> really<00:16:40.339> needed<00:16:40.820> in<00:16:41.000> order<00:16:41.149> to 00:16:41.319 --> 00:16:41.329 align:start position:0% some sort was really needed in order to 00:16:41.329 --> 00:16:46.030 align:start position:0% some sort was really needed in order to assure<00:16:41.660> that<00:16:42.490> fire<00:16:43.490> safety<00:16:43.910> and<00:16:44.269> other<00:16:45.040> you 00:16:46.030 --> 00:16:46.040 align:start position:0% assure that fire safety and other you 00:16:46.040 --> 00:16:48.430 align:start position:0% assure that fire safety and other you know<00:16:46.070> safety<00:16:46.730> aspects<00:16:47.269> were<00:16:47.450> adequately 00:16:48.430 --> 00:16:48.440 align:start position:0% know safety aspects were adequately 00:16:48.440 --> 00:16:53.920 align:start position:0% know safety aspects were adequately covered<00:16:48.950> then<00:16:49.910> a<00:16:52.060> road<00:16:53.060> connection<00:16:53.750> that 00:16:53.920 --> 00:16:53.930 align:start position:0% covered then a road connection that 00:16:53.930 --> 00:16:57.519 align:start position:0% covered then a road connection that would<00:16:54.110> be<00:16:54.620> for<00:16:55.010> emergency<00:16:55.700> access<00:16:55.880> only<00:16:56.529> would 00:16:57.519 --> 00:16:57.529 align:start position:0% would be for emergency access only would 00:16:57.529 --> 00:17:00.250 align:start position:0% would be for emergency access only would be<00:16:57.740> required<00:16:58.300> so<00:16:59.300> that<00:16:59.329> and<00:16:59.750> there's<00:16:59.990> several 00:17:00.250 --> 00:17:00.260 align:start position:0% be required so that and there's several 00:17:00.260 --> 00:17:01.990 align:start position:0% be required so that and there's several different<00:17:00.410> options<00:17:00.890> for<00:17:01.279> how<00:17:01.519> that<00:17:01.760> can<00:17:01.940> be 00:17:01.990 --> 00:17:02.000 align:start position:0% different options for how that can be 00:17:02.000 --> 00:17:03.519 align:start position:0% different options for how that can be done<00:17:02.329> it<00:17:02.630> wouldn't<00:17:02.930> be<00:17:03.050> the<00:17:03.260> type<00:17:03.500> of 00:17:03.519 --> 00:17:03.529 align:start position:0% done it wouldn't be the type of 00:17:03.529 --> 00:17:07.150 align:start position:0% done it wouldn't be the type of connection<00:17:04.100> that<00:17:04.480> would<00:17:05.480> have<00:17:06.079> the<00:17:06.410> traffic 00:17:07.150 --> 00:17:07.160 align:start position:0% connection that would have the traffic 00:17:07.160 --> 00:17:08.740 align:start position:0% connection that would have the traffic from<00:17:07.280> the<00:17:07.400> neighborhood<00:17:07.760> flowing<00:17:08.329> through<00:17:08.569> it 00:17:08.740 --> 00:17:08.750 align:start position:0% from the neighborhood flowing through it 00:17:08.750 --> 00:17:12.069 align:start position:0% from the neighborhood flowing through it and<00:17:09.500> mr.<00:17:10.429> Jensen<00:17:10.819> can<00:17:11.000> talk<00:17:11.209> talk<00:17:11.750> more<00:17:11.990> about 00:17:12.069 --> 00:17:12.079 align:start position:0% and mr. Jensen can talk talk more about 00:17:12.079 --> 00:17:13.960 align:start position:0% and mr. Jensen can talk talk more about some<00:17:12.439> of<00:17:12.559> the<00:17:12.620> different<00:17:12.919> options<00:17:13.309> but<00:17:13.880> it 00:17:13.960 --> 00:17:13.970 align:start position:0% some of the different options but it 00:17:13.970 --> 00:17:17.199 align:start position:0% some of the different options but it would<00:17:14.089> basically<00:17:14.299> be<00:17:14.660> a<00:17:14.839> connection<00:17:15.559> or<00:17:16.209> some 00:17:17.199 --> 00:17:17.209 align:start position:0% would basically be a connection or some 00:17:17.209 --> 00:17:18.789 align:start position:0% would basically be a connection or some provision<00:17:17.839> so<00:17:18.020> that<00:17:18.199> if<00:17:18.319> there<00:17:18.500> were<00:17:18.650> an 00:17:18.789 --> 00:17:18.799 align:start position:0% provision so that if there were an 00:17:18.799 --> 00:17:20.590 align:start position:0% provision so that if there were an emergency<00:17:19.069> of<00:17:19.640> fire<00:17:19.880> emergency<00:17:20.480> or<00:17:20.569> something 00:17:20.590 --> 00:17:20.600 align:start position:0% emergency of fire emergency or something 00:17:20.600 --> 00:17:22.390 align:start position:0% emergency of fire emergency or something of<00:17:21.049> that<00:17:21.079> nature<00:17:21.230> it<00:17:21.679> would<00:17:21.770> be<00:17:21.890> an<00:17:22.010> area<00:17:22.370> that 00:17:22.390 --> 00:17:22.400 align:start position:0% of that nature it would be an area that 00:17:22.400 --> 00:17:26.140 align:start position:0% of that nature it would be an area that a<00:17:22.549> fire<00:17:22.760> truck<00:17:23.030> could<00:17:23.209> go<00:17:23.329> across<00:17:23.980> you<00:17:24.980> know<00:17:25.150> so 00:17:26.140 --> 00:17:26.150 align:start position:0% a fire truck could go across you know so 00:17:26.150 --> 00:17:28.120 align:start position:0% a fire truck could go across you know so that<00:17:26.179> we<00:17:26.900> could<00:17:27.110> get<00:17:27.290> into<00:17:27.589> the<00:17:27.679> neighborhood 00:17:28.120 --> 00:17:28.130 align:start position:0% that we could get into the neighborhood 00:17:28.130 --> 00:17:31.690 align:start position:0% that we could get into the neighborhood for<00:17:28.309> safety<00:17:28.750> but<00:17:29.750> not<00:17:30.320> regular<00:17:31.220> everyday 00:17:31.690 --> 00:17:31.700 align:start position:0% for safety but not regular everyday 00:17:31.700 --> 00:17:33.669 align:start position:0% for safety but not regular everyday traffic<00:17:32.390> as<00:17:32.600> part<00:17:32.929> of<00:17:32.990> the<00:17:33.080> traffic<00:17:33.350> pattern 00:17:33.669 --> 00:17:33.679 align:start position:0% traffic as part of the traffic pattern 00:17:33.679 --> 00:17:36.909 align:start position:0% traffic as part of the traffic pattern if<00:17:34.580> it<00:17:35.270> was<00:17:35.510> determined<00:17:36.169> in<00:17:36.260> one<00:17:36.440> of<00:17:36.470> the<00:17:36.679> tier 00:17:36.909 --> 00:17:36.919 align:start position:0% if it was determined in one of the tier 00:17:36.919 --> 00:17:39.039 align:start position:0% if it was determined in one of the tier 2<00:17:37.130> or<00:17:37.340> tier<00:17:37.520> 3<00:17:37.790> you<00:17:38.210> know<00:17:38.330> if<00:17:38.390> it<00:17:38.510> was<00:17:38.600> a<00:17:38.630> tier<00:17:38.900> 2 00:17:39.039 --> 00:17:39.049 align:start position:0% 2 or tier 3 you know if it was a tier 2 00:17:39.049 --> 00:17:43.030 align:start position:0% 2 or tier 3 you know if it was a tier 2 tier<00:17:39.080> 3<00:17:39.590> neighborhood<00:17:41.200> that<00:17:42.200> there<00:17:42.590> really 00:17:43.030 --> 00:17:43.040 align:start position:0% tier 3 neighborhood that there really 00:17:43.040 --> 00:17:46.690 align:start position:0% tier 3 neighborhood that there really wasn't<00:17:43.630> an<00:17:44.630> issue<00:17:45.500> of<00:17:45.740> that<00:17:46.010> nature<00:17:46.280> then 00:17:46.690 --> 00:17:46.700 align:start position:0% wasn't an issue of that nature then 00:17:46.700 --> 00:17:48.490 align:start position:0% wasn't an issue of that nature then there<00:17:46.850> wouldn't<00:17:47.090> be<00:17:47.240> a<00:17:47.419> road<00:17:47.720> requirement<00:17:48.380> at 00:17:48.490 --> 00:17:48.500 align:start position:0% there wouldn't be a road requirement at 00:17:48.500 --> 00:17:51.520 align:start position:0% there wouldn't be a road requirement at all<00:17:48.650> and<00:17:48.980> that's<00:17:49.549> a<00:17:49.940> that's<00:17:50.750> a<00:17:51.080> call<00:17:51.290> that 00:17:51.520 --> 00:17:51.530 align:start position:0% all and that's a that's a call that 00:17:51.530 --> 00:17:54.730 align:start position:0% all and that's a that's a call that would<00:17:51.650> that<00:17:52.010> would<00:17:52.070> be<00:17:52.370> made<00:17:52.660> at<00:17:53.660> the<00:17:54.110> time<00:17:54.140> and 00:17:54.730 --> 00:17:54.740 align:start position:0% would that would be made at the time and 00:17:54.740 --> 00:17:58.419 align:start position:0% would that would be made at the time and looking<00:17:55.570> looking<00:17:56.570> at<00:17:56.780> the<00:17:57.020> site<00:17:57.590> plan<00:17:57.770> or<00:17:58.250> the 00:17:58.419 --> 00:17:58.429 align:start position:0% looking looking at the site plan or the 00:17:58.429 --> 00:18:01.900 align:start position:0% looking looking at the site plan or the at<00:17:59.299> the<00:17:59.450> rezoning<00:17:59.840> stage<00:18:00.260> to<00:18:00.530> see<00:18:00.710> what<00:18:01.040> tier 00:18:01.900 --> 00:18:01.910 align:start position:0% at the rezoning stage to see what tier 00:18:01.910 --> 00:18:04.840 align:start position:0% at the rezoning stage to see what tier did<00:18:02.240> that<00:18:02.390> neighborhood<00:18:02.840> fall<00:18:03.049> into<00:18:03.850> ok 00:18:04.840 --> 00:18:04.850 align:start position:0% did that neighborhood fall into ok 00:18:04.850 --> 00:18:06.400 align:start position:0% did that neighborhood fall into ok because<00:18:05.210> the<00:18:05.419> way<00:18:05.540> it's<00:18:05.660> written<00:18:05.750> is<00:18:06.080> just<00:18:06.320> a 00:18:06.400 --> 00:18:06.410 align:start position:0% because the way it's written is just a 00:18:06.410 --> 00:18:07.960 align:start position:0% because the way it's written is just a little<00:18:06.590> bit<00:18:06.770> confusing<00:18:07.250> I<00:18:07.460> guess<00:18:07.640> that's<00:18:07.880> just 00:18:07.960 --> 00:18:07.970 align:start position:0% little bit confusing I guess that's just 00:18:07.970 --> 00:18:10.770 align:start position:0% little bit confusing I guess that's just a<00:18:08.240> technicality<00:18:08.419> because<00:18:09.140> it<00:18:09.380> basically<00:18:09.500> says 00:18:10.770 --> 00:18:10.780 align:start position:0% a technicality because it basically says 00:18:10.780 --> 00:18:14.740 align:start position:0% a technicality because it basically says you<00:18:11.780> know<00:18:11.900> if<00:18:12.169> a<00:18:12.860> potential<00:18:13.790> public<00:18:14.000> safety 00:18:14.740 --> 00:18:14.750 align:start position:0% you know if a potential public safety 00:18:14.750 --> 00:18:17.530 align:start position:0% you know if a potential public safety issue<00:18:14.960> has<00:18:15.320> been<00:18:15.470> identified<00:18:16.240> you<00:18:17.240> are<00:18:17.360> never 00:18:17.530 --> 00:18:17.540 align:start position:0% issue has been identified you are never 00:18:17.540 --> 00:18:19.830 align:start position:0% issue has been identified you are never a<00:18:17.660> tear<00:18:17.990> to<00:18:18.140> recruit<00:18:18.530> you're<00:18:18.710> always<00:18:19.010> a<00:18:19.040> tier<00:18:19.370> 1 00:18:19.830 --> 00:18:19.840 align:start position:0% a tear to recruit you're always a tier 1 00:18:19.840 --> 00:18:21.820 align:start position:0% a tear to recruit you're always a tier 1 because<00:18:20.840> you<00:18:20.929> have<00:18:21.080> to<00:18:21.230> meet<00:18:21.410> all<00:18:21.620> these 00:18:21.820 --> 00:18:21.830 align:start position:0% because you have to meet all these 00:18:21.830 --> 00:18:23.590 align:start position:0% because you have to meet all these criteria<00:18:22.520> so<00:18:22.790> it's<00:18:23.000> just<00:18:23.090> something<00:18:23.419> for<00:18:23.540> you 00:18:23.590 --> 00:18:23.600 align:start position:0% criteria so it's just something for you 00:18:23.600 --> 00:18:26.980 align:start position:0% criteria so it's just something for you to<00:18:23.690> look<00:18:23.780> at<00:18:24.049> well<00:18:24.230> the<00:18:25.210> criteria<00:18:26.210> for<00:18:26.270> all 00:18:26.980 --> 00:18:26.990 align:start position:0% to look at well the criteria for all 00:18:26.990 --> 00:18:31.510 align:start position:0% to look at well the criteria for all cases<00:18:27.500> for<00:18:28.130> a<00:18:28.160> tier<00:18:28.660> for<00:18:29.660> a<00:18:29.690> tier<00:18:30.220> the<00:18:31.220> tier<00:18:31.460> 1 00:18:31.510 --> 00:18:31.520 align:start position:0% cases for a tier for a tier the tier 1 00:18:31.520 --> 00:18:34.000 align:start position:0% cases for a tier for a tier the tier 1 is<00:18:31.940> if<00:18:32.090> you<00:18:32.210> don't<00:18:32.240> qualify<00:18:32.929> as<00:18:33.320> it<00:18:33.559> here<00:18:33.770> too 00:18:34.000 --> 00:18:34.010 align:start position:0% is if you don't qualify as it here too 00:18:34.010 --> 00:18:36.880 align:start position:0% is if you don't qualify as it here too and<00:18:34.280> in<00:18:34.520> all<00:18:34.790> cases<00:18:34.820> the<00:18:35.600> tier<00:18:35.870> or<00:18:36.049> a<00:18:36.140> tier<00:18:36.440> 2<00:18:36.650> or 00:18:36.880 --> 00:18:36.890 align:start position:0% and in all cases the tier or a tier 2 or 00:18:36.890 --> 00:18:44.830 align:start position:0% and in all cases the tier or a tier 2 or 3<00:18:37.480> the<00:18:40.210> the<00:18:41.890> primary<00:18:42.940> criteria<00:18:43.940> between<00:18:44.419> that 00:18:44.830 --> 00:18:44.840 align:start position:0% 3 the the primary criteria between that 00:18:44.840 --> 00:18:47.110 align:start position:0% 3 the the primary criteria between that gets<00:18:45.050> you<00:18:45.230> into<00:18:45.410> either<00:18:45.770> a<00:18:45.890> two<00:18:46.190> or<00:18:46.220> a<00:18:46.429> three<00:18:46.520> is 00:18:47.110 --> 00:18:47.120 align:start position:0% gets you into either a two or a three is 00:18:47.120 --> 00:18:47.529 align:start position:0% gets you into either a two or a three is the 00:18:47.529 --> 00:18:47.539 align:start position:0% the 00:18:47.539 --> 00:18:49.840 align:start position:0% the date<00:18:48.049> of<00:18:48.259> the<00:18:48.379> development<00:18:49.070> plan<00:18:49.190> approval 00:18:49.840 --> 00:18:49.850 align:start position:0% date of the development plan approval 00:18:49.850 --> 00:18:52.450 align:start position:0% date of the development plan approval the<00:18:49.999> january<00:18:50.389> fourteenth<00:18:50.869> day<00:18:51.109> and<00:18:51.379> the<00:18:52.220> fact 00:18:52.450 --> 00:18:52.460 align:start position:0% the january fourteenth day and the fact 00:18:52.460 --> 00:18:55.690 align:start position:0% the january fourteenth day and the fact that<00:18:52.960> there's<00:18:53.960> not<00:18:54.200> an<00:18:54.470> existing<00:18:55.070> street<00:18:55.399> stub 00:18:55.690 --> 00:18:55.700 align:start position:0% that there's not an existing street stub 00:18:55.700 --> 00:18:57.489 align:start position:0% that there's not an existing street stub that<00:18:55.729> goes<00:18:56.090> to<00:18:56.269> the<00:18:56.299> property<00:18:56.809> line<00:18:56.960> so<00:18:57.289> that's 00:18:57.489 --> 00:18:57.499 align:start position:0% that goes to the property line so that's 00:18:57.499 --> 00:19:00.899 align:start position:0% that goes to the property line so that's a<00:18:57.710> key<00:18:58.220> piece<00:18:58.549> of<00:18:58.759> it<00:18:58.940> so<00:18:59.149> those<00:18:59.419> both<00:19:00.139> of<00:19:00.440> those 00:19:00.899 --> 00:19:00.909 align:start position:0% a key piece of it so those both of those 00:19:00.909 --> 00:19:05.049 align:start position:0% a key piece of it so those both of those criteria<00:19:02.049> would<00:19:03.049> have<00:19:03.369> would<00:19:04.369> have<00:19:04.549> to<00:19:04.700> be<00:19:04.850> met 00:19:05.049 --> 00:19:05.059 align:start position:0% criteria would have would have to be met 00:19:05.059 --> 00:19:07.330 align:start position:0% criteria would have would have to be met in<00:19:05.239> order<00:19:05.359> to<00:19:05.600> be<00:19:05.720> either<00:19:05.899> tier<00:19:06.320> to<00:19:06.739> be<00:19:06.889> tier<00:19:07.129> 2 00:19:07.330 --> 00:19:07.340 align:start position:0% in order to be either tier to be tier 2 00:19:07.340 --> 00:19:11.259 align:start position:0% in order to be either tier to be tier 2 or<00:19:07.580> tier<00:19:07.850> 3<00:19:08.149> and<00:19:08.799> then<00:19:09.799> once<00:19:10.279> you<00:19:10.549> get<00:19:10.850> to<00:19:11.090> that 00:19:11.259 --> 00:19:11.269 align:start position:0% or tier 3 and then once you get to that 00:19:11.269 --> 00:19:14.799 align:start position:0% or tier 3 and then once you get to that point<00:19:11.450> then<00:19:12.320> the<00:19:12.649> third<00:19:13.179> the<00:19:14.179> third<00:19:14.419> question 00:19:14.799 --> 00:19:14.809 align:start position:0% point then the third the third question 00:19:14.809 --> 00:19:17.259 align:start position:0% point then the third the third question basically<00:19:15.559> is<00:19:15.950> whether<00:19:16.580> or<00:19:16.729> not<00:19:16.820> there's<00:19:17.119> the 00:19:17.259 --> 00:19:17.269 align:start position:0% basically is whether or not there's the 00:19:17.269 --> 00:19:22.419 align:start position:0% basically is whether or not there's the public<00:19:17.629> safety<00:19:18.019> concern<00:19:18.580> okay<00:19:20.979> so<00:19:21.979> the<00:19:22.249> public 00:19:22.419 --> 00:19:22.429 align:start position:0% public safety concern okay so the public 00:19:22.429 --> 00:19:24.639 align:start position:0% public safety concern okay so the public safety<00:19:23.059> was<00:19:23.269> the<00:19:23.450> other<00:19:23.570> question<00:19:23.659> I<00:19:24.109> had<00:19:24.139> you 00:19:24.639 --> 00:19:24.649 align:start position:0% safety was the other question I had you 00:19:24.649 --> 00:19:26.049 align:start position:0% safety was the other question I had you know<00:19:24.799> and<00:19:25.009> I<00:19:25.159> knew<00:19:25.309> it<00:19:25.429> would<00:19:25.519> be<00:19:25.729> firing 00:19:26.049 --> 00:19:26.059 align:start position:0% know and I knew it would be firing 00:19:26.059 --> 00:19:29.109 align:start position:0% know and I knew it would be firing police<00:19:26.330> access<00:19:27.019> but<00:19:27.859> you<00:19:28.549> know<00:19:28.669> we've<00:19:28.879> seen 00:19:29.109 --> 00:19:29.119 align:start position:0% police access but you know we've seen 00:19:29.119 --> 00:19:31.389 align:start position:0% police access but you know we've seen some<00:19:29.299> cases<00:19:29.809> where<00:19:30.049> we<00:19:30.259> had<00:19:30.529> an<00:19:30.799> existing 00:19:31.389 --> 00:19:31.399 align:start position:0% some cases where we had an existing 00:19:31.399 --> 00:19:33.879 align:start position:0% some cases where we had an existing older<00:19:31.789> neighborhood<00:19:32.299> that<00:19:33.169> was<00:19:33.679> well 00:19:33.879 --> 00:19:33.889 align:start position:0% older neighborhood that was well 00:19:33.889 --> 00:19:36.009 align:start position:0% older neighborhood that was well established<00:19:34.070> there's<00:19:34.909> a<00:19:34.999> light<00:19:35.269> where<00:19:35.690> people 00:19:36.009 --> 00:19:36.019 align:start position:0% established there's a light where people 00:19:36.019 --> 00:19:37.749 align:start position:0% established there's a light where people can<00:19:36.229> get<00:19:36.409> in<00:19:36.619> and<00:19:36.799> out<00:19:36.859> they<00:19:37.070> face<00:19:37.279> a<00:19:37.309> busy 00:19:37.749 --> 00:19:37.759 align:start position:0% can get in and out they face a busy 00:19:37.759 --> 00:19:39.909 align:start position:0% can get in and out they face a busy street<00:19:38.179> and<00:19:38.539> then<00:19:39.200> there's<00:19:39.470> something 00:19:39.909 --> 00:19:39.919 align:start position:0% street and then there's something 00:19:39.919 --> 00:19:42.399 align:start position:0% street and then there's something developed<00:19:40.369> right<00:19:40.580> next<00:19:40.999> to<00:19:41.210> it<00:19:41.239> and<00:19:41.570> those 00:19:42.399 --> 00:19:42.409 align:start position:0% developed right next to it and those 00:19:42.409 --> 00:19:43.539 align:start position:0% developed right next to it and those people<00:19:42.590> aren't<00:19:42.859> going<00:19:43.009> to<00:19:43.099> get<00:19:43.190> a<00:19:43.249> traffic 00:19:43.539 --> 00:19:43.549 align:start position:0% people aren't going to get a traffic 00:19:43.549 --> 00:19:45.369 align:start position:0% people aren't going to get a traffic light<00:19:43.940> to<00:19:44.210> get<00:19:44.330> in<00:19:44.509> and<00:19:44.690> out<00:19:44.779> because<00:19:45.139> it<00:19:45.259> would 00:19:45.369 --> 00:19:45.379 align:start position:0% light to get in and out because it would 00:19:45.379 --> 00:19:47.710 align:start position:0% light to get in and out because it would be<00:19:45.409> too<00:19:45.529> close<00:19:46.009> yet<00:19:46.759> the<00:19:46.970> older<00:19:47.239> neighborhood 00:19:47.710 --> 00:19:47.720 align:start position:0% be too close yet the older neighborhood 00:19:47.720 --> 00:19:49.629 align:start position:0% be too close yet the older neighborhood is<00:19:47.869> saying<00:19:48.109> no<00:19:48.349> you<00:19:48.379> can't<00:19:48.859> connect<00:19:49.249> to<00:19:49.340> us 00:19:49.629 --> 00:19:49.639 align:start position:0% is saying no you can't connect to us 00:19:49.639 --> 00:19:52.599 align:start position:0% is saying no you can't connect to us which<00:19:50.419> kind<00:19:50.779> of<00:19:50.960> creates<00:19:51.409> a<00:19:51.590> safety<00:19:52.009> issue<00:19:52.159> for 00:19:52.599 --> 00:19:52.609 align:start position:0% which kind of creates a safety issue for 00:19:52.609 --> 00:19:54.820 align:start position:0% which kind of creates a safety issue for the<00:19:52.729> new<00:19:52.879> neighborhood<00:19:53.389> you<00:19:54.200> know<00:19:54.349> they<00:19:54.619> have 00:19:54.820 --> 00:19:54.830 align:start position:0% the new neighborhood you know they have 00:19:54.830 --> 00:19:56.769 align:start position:0% the new neighborhood you know they have trouble<00:19:55.249> getting<00:19:55.369> in<00:19:55.759> and<00:19:55.940> out<00:19:56.029> on<00:19:56.269> this<00:19:56.389> busy 00:19:56.769 --> 00:19:56.779 align:start position:0% trouble getting in and out on this busy 00:19:56.779 --> 00:19:58.749 align:start position:0% trouble getting in and out on this busy street<00:19:57.039> whereas<00:19:58.039> if<00:19:58.070> they're<00:19:58.429> a<00:19:58.460> you<00:19:58.669> know 00:19:58.749 --> 00:19:58.759 align:start position:0% street whereas if they're a you know 00:19:58.759 --> 00:20:00.369 align:start position:0% street whereas if they're a you know simple<00:19:59.119> connection<00:19:59.629> could<00:19:59.929> take<00:20:00.169> them 00:20:00.369 --> 00:20:00.379 align:start position:0% simple connection could take them 00:20:00.379 --> 00:20:02.499 align:start position:0% simple connection could take them through<00:20:00.590> the<00:20:00.679> older<00:20:01.099> neighborhood<00:20:01.609> and<00:20:01.849> out 00:20:02.499 --> 00:20:02.509 align:start position:0% through the older neighborhood and out 00:20:02.509 --> 00:20:05.169 align:start position:0% through the older neighborhood and out through<00:20:02.809> a<00:20:02.899> light<00:20:03.229> but<00:20:04.220> it<00:20:04.460> sounds<00:20:04.879> to<00:20:04.909> me<00:20:05.029> like 00:20:05.169 --> 00:20:05.179 align:start position:0% through a light but it sounds to me like 00:20:05.179 --> 00:20:07.239 align:start position:0% through a light but it sounds to me like that<00:20:05.659> would<00:20:05.869> never<00:20:06.080> be<00:20:06.289> a<00:20:06.320> consideration<00:20:06.950> it 00:20:07.239 --> 00:20:07.249 align:start position:0% that would never be a consideration it 00:20:07.249 --> 00:20:11.889 align:start position:0% that would never be a consideration it has<00:20:07.399> to<00:20:07.609> be<00:20:07.789> fire<00:20:08.659> safe<00:20:09.109> firearm<00:20:09.649> I<00:20:10.249> would<00:20:10.899> ask 00:20:11.889 --> 00:20:11.899 align:start position:0% has to be fire safe firearm I would ask 00:20:11.899 --> 00:20:16.289 align:start position:0% has to be fire safe firearm I would ask if<00:20:12.289> mr.<00:20:12.799> Jensen<00:20:13.220> has<00:20:13.369> anything<00:20:13.669> to<00:20:14.059> add<00:20:14.090> to 00:20:16.289 --> 00:20:16.299 align:start position:0% if mr. Jensen has anything to add to 00:20:16.299 --> 00:20:23.169 align:start position:0% if mr. Jensen has anything to add to that<00:20:17.299> decision<00:20:18.019> making<00:20:18.649> process<00:20:19.190> I<00:20:22.179> think 00:20:23.169 --> 00:20:23.179 align:start position:0% that decision making process I think 00:20:23.179 --> 00:20:24.820 align:start position:0% that decision making process I think what<00:20:23.330> we<00:20:23.419> need<00:20:23.450> to<00:20:23.570> do<00:20:23.720> is<00:20:23.809> focus<00:20:24.049> on<00:20:24.409> the<00:20:24.529> older 00:20:24.820 --> 00:20:24.830 align:start position:0% what we need to do is focus on the older 00:20:24.830 --> 00:20:27.190 align:start position:0% what we need to do is focus on the older neighborhood<00:20:25.309> as<00:20:25.519> a<00:20:26.239> way<00:20:26.479> this<00:20:26.659> ordinance<00:20:27.139> is 00:20:27.190 --> 00:20:27.200 align:start position:0% neighborhood as a way this ordinance is 00:20:27.200 --> 00:20:28.839 align:start position:0% neighborhood as a way this ordinance is written<00:20:27.529> it<00:20:27.590> seems<00:20:28.129> to<00:20:28.369> provide<00:20:28.609> them 00:20:28.839 --> 00:20:28.849 align:start position:0% written it seems to provide them 00:20:28.849 --> 00:20:33.339 align:start position:0% written it seems to provide them protections<00:20:29.450> so<00:20:30.580> again<00:20:31.929> those<00:20:32.929> protections 00:20:33.339 --> 00:20:33.349 align:start position:0% protections so again those protections 00:20:33.349 --> 00:20:36.369 align:start position:0% protections so again those protections would<00:20:33.649> be<00:20:34.090> not<00:20:35.090> allowing<00:20:35.450> vehicular<00:20:35.899> traffic 00:20:36.369 --> 00:20:36.379 align:start position:0% would be not allowing vehicular traffic 00:20:36.379 --> 00:20:38.200 align:start position:0% would be not allowing vehicular traffic dick<00:20:36.710> to<00:20:36.950> penetrate<00:20:37.460> into<00:20:37.609> their<00:20:37.909> older 00:20:38.200 --> 00:20:38.210 align:start position:0% dick to penetrate into their older 00:20:38.210 --> 00:20:40.839 align:start position:0% dick to penetrate into their older neighborhood<00:20:39.009> only<00:20:40.009> in<00:20:40.099> those<00:20:40.220> cases<00:20:40.460> where 00:20:40.839 --> 00:20:40.849 align:start position:0% neighborhood only in those cases where 00:20:40.849 --> 00:20:43.119 align:start position:0% neighborhood only in those cases where some<00:20:41.509> sort<00:20:41.720> of<00:20:41.779> emergency<00:20:41.960> access<00:20:42.379> is<00:20:42.769> needed 00:20:43.119 --> 00:20:43.129 align:start position:0% some sort of emergency access is needed 00:20:43.129 --> 00:20:45.180 align:start position:0% some sort of emergency access is needed so<00:20:43.279> in<00:20:43.429> that<00:20:43.519> particular<00:20:43.639> case<00:20:43.940> it<00:20:44.389> would<00:20:44.539> be 00:20:45.180 --> 00:20:45.190 align:start position:0% so in that particular case it would be 00:20:45.190 --> 00:20:47.229 align:start position:0% so in that particular case it would be you<00:20:46.190> know<00:20:46.309> could<00:20:46.519> be<00:20:46.639> hard<00:20:46.879> for<00:20:47.059> the<00:20:47.119> new 00:20:47.229 --> 00:20:47.239 align:start position:0% you know could be hard for the new 00:20:47.239 --> 00:20:48.669 align:start position:0% you know could be hard for the new neighborhood<00:20:47.720> because<00:20:48.080> they<00:20:48.259> don't<00:20:48.440> enjoy 00:20:48.669 --> 00:20:48.679 align:start position:0% neighborhood because they don't enjoy 00:20:48.679 --> 00:20:50.710 align:start position:0% neighborhood because they don't enjoy the<00:20:48.830> printing<00:20:49.220> of<00:20:49.279> the<00:20:49.340> the<00:20:49.879> provisions<00:20:50.659> for 00:20:50.710 --> 00:20:50.720 align:start position:0% the printing of the the provisions for 00:20:50.720 --> 00:20:52.719 align:start position:0% the printing of the the provisions for us<00:20:50.989> for<00:20:51.320> a<00:20:51.349> light<00:20:51.590> to<00:20:51.769> go<00:20:51.919> out<00:20:52.099> to<00:20:52.340> so 00:20:52.719 --> 00:20:52.729 align:start position:0% us for a light to go out to so 00:20:52.729 --> 00:20:53.889 align:start position:0% us for a light to go out to so unfortunately<00:20:53.179> that's<00:20:53.599> the<00:20:53.690> way<00:20:53.869> our 00:20:53.889 --> 00:20:53.899 align:start position:0% unfortunately that's the way our 00:20:53.899 --> 00:20:57.220 align:start position:0% unfortunately that's the way our ordinance<00:20:54.440> is<00:20:54.590> written<00:20:54.889> but<00:20:55.669> the<00:20:55.940> as<00:20:56.869> far<00:20:57.109> as 00:20:57.220 --> 00:20:57.230 align:start position:0% ordinance is written but the as far as 00:20:57.230 --> 00:20:59.589 align:start position:0% ordinance is written but the as far as who<00:20:57.349> you<00:20:58.070> know<00:20:58.460> the<00:20:58.609> departments<00:20:59.179> that<00:20:59.239> that 00:20:59.589 --> 00:20:59.599 align:start position:0% who you know the departments that that 00:20:59.599 --> 00:21:00.860 align:start position:0% who you know the departments that that were<00:20:59.659> responsible<00:21:00.200> for<00:21:00.320> determining 00:21:00.860 --> 00:21:00.870 align:start position:0% were responsible for determining 00:21:00.870 --> 00:21:02.840 align:start position:0% were responsible for determining tyr<00:21:01.140> neighborhood<00:21:01.590> it<00:21:01.710> is<00:21:01.860> it<00:21:02.370> resides 00:21:02.840 --> 00:21:02.850 align:start position:0% tyr neighborhood it is it resides 00:21:02.850 --> 00:21:04.190 align:start position:0% tyr neighborhood it is it resides currently<00:21:03.450> in<00:21:03.570> the<00:21:03.690> transportation 00:21:04.190 --> 00:21:04.200 align:start position:0% currently in the transportation 00:21:04.200 --> 00:21:06.500 align:start position:0% currently in the transportation facilities<00:21:04.950> Department<00:21:05.460> is<00:21:05.850> the<00:21:05.970> way<00:21:06.059> the<00:21:06.210> way 00:21:06.500 --> 00:21:06.510 align:start position:0% facilities Department is the way the way 00:21:06.510 --> 00:21:08.660 align:start position:0% facilities Department is the way the way the<00:21:06.630> text<00:21:06.900> is<00:21:06.990> written<00:21:07.170> so<00:21:07.380> although<00:21:08.160> the 00:21:08.660 --> 00:21:08.670 align:start position:0% the text is written so although the 00:21:08.670 --> 00:21:10.190 align:start position:0% the text is written so although the transportation<00:21:09.510> and<00:21:09.630> traffic<00:21:09.900> engineering 00:21:10.190 --> 00:21:10.200 align:start position:0% transportation and traffic engineering 00:21:10.200 --> 00:21:12.470 align:start position:0% transportation and traffic engineering staff<00:21:10.410> will<00:21:10.590> do<00:21:10.710> an<00:21:10.800> evaluation<00:21:11.010> but<00:21:11.610> we<00:21:12.240> will 00:21:12.470 --> 00:21:12.480 align:start position:0% staff will do an evaluation but we will 00:21:12.480 --> 00:21:14.150 align:start position:0% staff will do an evaluation but we will have<00:21:12.530> consultation<00:21:13.530> with<00:21:13.710> all<00:21:13.860> the<00:21:14.010> other 00:21:14.150 --> 00:21:14.160 align:start position:0% have consultation with all the other 00:21:14.160 --> 00:21:16.040 align:start position:0% have consultation with all the other departments<00:21:14.730> you<00:21:15.330> know<00:21:15.390> within<00:21:15.570> the<00:21:15.750> town<00:21:15.930> of 00:21:16.040 --> 00:21:16.050 align:start position:0% departments you know within the town of 00:21:16.050 --> 00:21:17.270 align:start position:0% departments you know within the town of cary<00:21:16.260> including<00:21:16.680> the<00:21:16.770> fire<00:21:16.980> police 00:21:17.270 --> 00:21:17.280 align:start position:0% cary including the fire police 00:21:17.280 --> 00:21:19.970 align:start position:0% cary including the fire police department<00:21:17.870> if<00:21:18.870> that<00:21:19.050> helps<00:21:19.230> you<00:21:19.320> out<00:21:19.350> in<00:21:19.650> okay 00:21:19.970 --> 00:21:19.980 align:start position:0% department if that helps you out in okay 00:21:19.980 --> 00:21:25.310 align:start position:0% department if that helps you out in okay I<00:21:22.730> got<00:21:23.730> the<00:21:23.820> question<00:21:24.240> just<00:21:24.630> an<00:21:24.809> idea<00:21:24.990> popped 00:21:25.310 --> 00:21:25.320 align:start position:0% I got the question just an idea popped 00:21:25.320 --> 00:21:27.880 align:start position:0% I got the question just an idea popped into<00:21:25.530> my<00:21:25.680> mind<00:21:25.710> which<00:21:26.640> is<00:21:26.790> a<00:21:26.820> dangerous<00:21:27.150> thing 00:21:27.880 --> 00:21:27.890 align:start position:0% into my mind which is a dangerous thing 00:21:27.890 --> 00:21:30.260 align:start position:0% into my mind which is a dangerous thing railroad<00:21:28.890> crossings<00:21:29.340> we<00:21:29.550> seem<00:21:29.730> to<00:21:29.880> have<00:21:29.910> had<00:21:30.240> a 00:21:30.260 --> 00:21:30.270 align:start position:0% railroad crossings we seem to have had a 00:21:30.270 --> 00:21:32.450 align:start position:0% railroad crossings we seem to have had a case<00:21:30.480> recently<00:21:30.660> where<00:21:30.960> okay<00:21:31.770> their<00:21:32.250> railroad 00:21:32.450 --> 00:21:32.460 align:start position:0% case recently where okay their railroad 00:21:32.460 --> 00:21:34.250 align:start position:0% case recently where okay their railroad was<00:21:32.760> thought<00:21:33.240> to<00:21:33.270> be<00:21:33.450> connected<00:21:33.720> but<00:21:33.960> didn't 00:21:34.250 --> 00:21:34.260 align:start position:0% was thought to be connected but didn't 00:21:34.260 --> 00:21:35.570 align:start position:0% was thought to be connected but didn't and<00:21:34.500> I<00:21:34.559> think<00:21:34.770> in<00:21:34.860> the<00:21:34.950> future<00:21:34.980> there<00:21:35.370> might<00:21:35.550> be 00:21:35.570 --> 00:21:35.580 align:start position:0% and I think in the future there might be 00:21:35.580 --> 00:21:39.710 align:start position:0% and I think in the future there might be more<00:21:35.940> a<00:21:37.190> goal<00:21:38.190> is<00:21:38.370> to<00:21:38.520> close<00:21:38.700> more<00:21:39.000> my<00:21:39.420> correct 00:21:39.710 --> 00:21:39.720 align:start position:0% more a goal is to close more my correct 00:21:39.720 --> 00:21:41.240 align:start position:0% more a goal is to close more my correct in<00:21:39.809> saying<00:21:39.960> that<00:21:40.170> to<00:21:40.320> make<00:21:40.440> it<00:21:40.620> safer<00:21:40.980> for<00:21:41.010> them 00:21:41.240 --> 00:21:41.250 align:start position:0% in saying that to make it safer for them 00:21:41.250 --> 00:21:43.640 align:start position:0% in saying that to make it safer for them so<00:21:42.150> do<00:21:42.420> we<00:21:42.570> worry<00:21:43.020> about<00:21:43.230> that<00:21:43.380> of<00:21:43.500> all<00:21:43.620> the 00:21:43.640 --> 00:21:43.650 align:start position:0% so do we worry about that of all the 00:21:43.650 --> 00:21:46.430 align:start position:0% so do we worry about that of all the things<00:21:43.950> I<00:21:44.100> think<00:21:44.280> it<00:21:44.400> in<00:21:44.730> cary<00:21:45.059> we're<00:21:45.360> we<00:21:46.200> want 00:21:46.430 --> 00:21:46.440 align:start position:0% things I think it in cary we're we want 00:21:46.440 --> 00:21:48.320 align:start position:0% things I think it in cary we're we want to<00:21:46.530> close<00:21:46.740> any<00:21:46.950> rail<00:21:47.520> crossings<00:21:48.059> because 00:21:48.320 --> 00:21:48.330 align:start position:0% to close any rail crossings because 00:21:48.330 --> 00:21:50.180 align:start position:0% to close any rail crossings because obviously<00:21:49.290> we've<00:21:49.590> got<00:21:49.740> to<00:21:49.830> move<00:21:49.920> traffic 00:21:50.180 --> 00:21:50.190 align:start position:0% obviously we've got to move traffic 00:21:50.190 --> 00:21:53.630 align:start position:0% obviously we've got to move traffic around<00:21:50.640> this<00:21:50.880> this<00:21:51.330> major<00:21:52.460> corridors<00:21:53.460> that 00:21:53.630 --> 00:21:53.640 align:start position:0% around this this major corridors that 00:21:53.640 --> 00:21:55.880 align:start position:0% around this this major corridors that penetrate<00:21:54.120> different<00:21:54.450> parts<00:21:54.660> of<00:21:54.750> town<00:21:54.929> so<00:21:55.320> we 00:21:55.880 --> 00:21:55.890 align:start position:0% penetrate different parts of town so we 00:21:55.890 --> 00:21:57.530 align:start position:0% penetrate different parts of town so we look<00:21:56.070> for<00:21:56.280> ways<00:21:56.400> to<00:21:56.460> navigate<00:21:56.760> through<00:21:57.360> them 00:21:57.530 --> 00:21:57.540 align:start position:0% look for ways to navigate through them 00:21:57.540 --> 00:21:58.760 align:start position:0% look for ways to navigate through them either<00:21:57.780> through<00:21:58.110> an<00:21:58.380> at-grade<00:21:58.590> crossings 00:21:58.760 --> 00:21:58.770 align:start position:0% either through an at-grade crossings 00:21:58.770 --> 00:22:01.520 align:start position:0% either through an at-grade crossings aura<00:21:59.429> or<00:21:59.730> grade-separated<00:22:00.480> crossing<00:22:01.320> but 00:22:01.520 --> 00:22:01.530 align:start position:0% aura or grade-separated crossing but 00:22:01.530 --> 00:22:03.919 align:start position:0% aura or grade-separated crossing but there<00:22:02.460> has<00:22:02.640> been<00:22:02.880> a<00:22:02.910> movement<00:22:03.240> across<00:22:03.570> North 00:22:03.919 --> 00:22:03.929 align:start position:0% there has been a movement across North 00:22:03.929 --> 00:22:06.590 align:start position:0% there has been a movement across North Carolina<00:22:04.320> in<00:22:04.500> general<00:22:04.890> to<00:22:05.070> close<00:22:05.600> certain 00:22:06.590 --> 00:22:06.600 align:start position:0% Carolina in general to close certain 00:22:06.600 --> 00:22:08.780 align:start position:0% Carolina in general to close certain railroad<00:22:07.350> crossings<00:22:07.890> that<00:22:07.950> a<00:22:08.250> doesn't 00:22:08.780 --> 00:22:08.790 align:start position:0% railroad crossings that a doesn't 00:22:08.790 --> 00:22:10.960 align:start position:0% railroad crossings that a doesn't doesn't<00:22:08.940> have<00:22:09.150> any<00:22:09.270> really<00:22:09.510> traffic<00:22:10.410> benefit 00:22:10.960 --> 00:22:10.970 align:start position:0% doesn't have any really traffic benefit 00:22:10.970 --> 00:22:13.580 align:start position:0% doesn't have any really traffic benefit circulation<00:22:11.970> benefit<00:22:12.360> and<00:22:12.540> and<00:22:12.809> and<00:22:13.110> really 00:22:13.580 --> 00:22:13.590 align:start position:0% circulation benefit and and and really 00:22:13.590 --> 00:22:15.440 align:start position:0% circulation benefit and and and really to<00:22:13.770> kind<00:22:13.890> of<00:22:14.010> eliminate<00:22:14.370> those<00:22:14.400> those<00:22:15.000> hazards 00:22:15.440 --> 00:22:15.450 align:start position:0% to kind of eliminate those those hazards 00:22:15.450 --> 00:22:17.630 align:start position:0% to kind of eliminate those those hazards along<00:22:15.840> along<00:22:16.320> the<00:22:16.470> corridors<00:22:16.890> I<00:22:17.130> know<00:22:17.400> what<00:22:17.550> is 00:22:17.630 --> 00:22:17.640 align:start position:0% along along the corridors I know what is 00:22:17.640 --> 00:22:21.230 align:start position:0% along along the corridors I know what is that<00:22:17.790> doing<00:22:18.059> to<00:22:18.360> I<00:22:18.690> wonder<00:22:19.140> to<00:22:19.470> this<00:22:19.940> tier<00:22:20.940> and 00:22:21.230 --> 00:22:21.240 align:start position:0% that doing to I wonder to this tier and 00:22:21.240 --> 00:22:23.240 align:start position:0% that doing to I wonder to this tier and effective<00:22:21.900> is<00:22:22.050> it<00:22:22.260> really<00:22:22.470> hasn't<00:22:22.650> no<00:22:22.950> bearing 00:22:23.240 --> 00:22:23.250 align:start position:0% effective is it really hasn't no bearing 00:22:23.250 --> 00:22:25.070 align:start position:0% effective is it really hasn't no bearing in<00:22:23.370> it<00:22:23.490> because<00:22:23.610> that's<00:22:23.820> okay<00:22:24.450> again<00:22:24.900> this<00:22:25.020> is 00:22:25.070 --> 00:22:25.080 align:start position:0% in it because that's okay again this is 00:22:25.080 --> 00:22:26.510 align:start position:0% in it because that's okay again this is just<00:22:25.350> this<00:22:25.590> is<00:22:25.650> just<00:22:25.830> how<00:22:26.100> do<00:22:26.160> we<00:22:26.309> interact 00:22:26.510 --> 00:22:26.520 align:start position:0% just this is just how do we interact 00:22:26.520 --> 00:22:29.240 align:start position:0% just this is just how do we interact with<00:22:26.760> neighborhoods<00:22:27.590> again<00:22:28.590> if<00:22:28.740> there's<00:22:29.160> a 00:22:29.240 --> 00:22:29.250 align:start position:0% with neighborhoods again if there's a 00:22:29.250 --> 00:22:31.340 align:start position:0% with neighborhoods again if there's a major<00:22:29.580> obstacle<00:22:29.850> you<00:22:30.809> know<00:22:30.900> like<00:22:31.020> like<00:22:31.080> a 00:22:31.340 --> 00:22:31.350 align:start position:0% major obstacle you know like like a 00:22:31.350 --> 00:22:33.500 align:start position:0% major obstacle you know like like a railroad<00:22:31.620> than<00:22:32.010> how<00:22:32.640> we<00:22:32.670> how<00:22:33.120> do<00:22:33.179> we<00:22:33.330> get 00:22:33.500 --> 00:22:33.510 align:start position:0% railroad than how we how do we get 00:22:33.510 --> 00:22:35.270 align:start position:0% railroad than how we how do we get around<00:22:33.630> that<00:22:33.870> obstacle<00:22:34.380> is<00:22:34.710> is<00:22:34.980> just<00:22:35.130> a 00:22:35.270 --> 00:22:35.280 align:start position:0% around that obstacle is is just a 00:22:35.280 --> 00:22:43.360 align:start position:0% around that obstacle is is just a different<00:22:35.640> different<00:22:36.240> manner 00:22:43.360 --> 00:22:43.370 align:start position:0% 00:22:43.370 --> 00:22:46.660 align:start position:0% anything<00:22:44.210> else<00:22:44.330> have<00:22:44.930> a<00:22:44.990> quick<00:22:45.110> question<00:22:45.670> just 00:22:46.660 --> 00:22:46.670 align:start position:0% anything else have a quick question just 00:22:46.670 --> 00:22:48.070 align:start position:0% anything else have a quick question just with<00:22:46.790> your<00:22:46.880> acid<00:22:47.180> and<00:22:47.300> I<00:22:47.360> care<00:22:47.570> Memphis<00:22:47.930> was 00:22:48.070 --> 00:22:48.080 align:start position:0% with your acid and I care Memphis was 00:22:48.080 --> 00:22:50.680 align:start position:0% with your acid and I care Memphis was touched<00:22:48.320> on<00:22:48.530> during<00:22:48.860> our<00:22:48.980> workgroup<00:22:49.450> but<00:22:50.450> how 00:22:50.680 --> 00:22:50.690 align:start position:0% touched on during our workgroup but how 00:22:50.690 --> 00:22:52.000 align:start position:0% touched on during our workgroup but how does<00:22:50.750> this<00:22:50.960> ordinance<00:22:51.410> compare<00:22:51.770> it<00:22:51.860> to 00:22:52.000 --> 00:22:52.010 align:start position:0% does this ordinance compare it to 00:22:52.010 --> 00:22:53.770 align:start position:0% does this ordinance compare it to neighboring<00:22:52.460> other<00:22:53.000> communities<00:22:53.540> in<00:22:53.690> the 00:22:53.770 --> 00:22:53.780 align:start position:0% neighboring other communities in the 00:22:53.780 --> 00:22:55.660 align:start position:0% neighboring other communities in the area<00:22:53.809> is<00:22:54.410> this<00:22:54.860> kind<00:22:55.010> of<00:22:55.100> in<00:22:55.190> par<00:22:55.370> with<00:22:55.640> what 00:22:55.660 --> 00:22:55.670 align:start position:0% area is this kind of in par with what 00:22:55.670 --> 00:22:59.380 align:start position:0% area is this kind of in par with what they're<00:22:56.120> doing<00:22:56.450> or<00:22:56.480> I<00:22:57.170> think<00:22:57.740> yeah<00:22:58.280> I'm<00:22:59.120> not 00:22:59.380 --> 00:22:59.390 align:start position:0% they're doing or I think yeah I'm not 00:22:59.390 --> 00:23:00.850 align:start position:0% they're doing or I think yeah I'm not familiar<00:22:59.600> with<00:22:59.990> although<00:23:00.200> our<00:23:00.500> neighboring 00:23:00.850 --> 00:23:00.860 align:start position:0% familiar with although our neighboring 00:23:00.860 --> 00:23:04.510 align:start position:0% familiar with although our neighboring because<00:23:01.010> this<00:23:01.150> is<00:23:02.150> changing<00:23:02.690> i<00:23:02.780> have<00:23:03.110> i<00:23:03.520> have 00:23:04.510 --> 00:23:04.520 align:start position:0% because this is changing i have i have 00:23:04.520 --> 00:23:07.690 align:start position:0% because this is changing i have i have been<00:23:04.940> had<00:23:05.930> conversations<00:23:06.890> with<00:23:06.920> several 00:23:07.690 --> 00:23:07.700 align:start position:0% been had conversations with several 00:23:07.700 --> 00:23:09.250 align:start position:0% been had conversations with several jurisdictions<00:23:07.910> they're<00:23:08.540> they're<00:23:08.809> grasping 00:23:09.250 --> 00:23:09.260 align:start position:0% jurisdictions they're they're grasping 00:23:09.260 --> 00:23:12.070 align:start position:0% jurisdictions they're they're grasping with<00:23:09.530> the<00:23:09.650> same<00:23:09.890> issue<00:23:10.280> of<00:23:10.700> how<00:23:11.540> to<00:23:11.600> how<00:23:12.050> to 00:23:12.070 --> 00:23:12.080 align:start position:0% with the same issue of how to how to 00:23:12.080 --> 00:23:14.260 align:start position:0% with the same issue of how to how to look<00:23:12.380> at<00:23:12.559> connectivity<00:23:13.550> in<00:23:13.700> a<00:23:13.790> different<00:23:14.120> way 00:23:14.260 --> 00:23:14.270 align:start position:0% look at connectivity in a different way 00:23:14.270 --> 00:23:16.240 align:start position:0% look at connectivity in a different way particularly<00:23:15.230> maybe<00:23:15.410> during<00:23:15.800> the<00:23:15.950> rezoning 00:23:16.240 --> 00:23:16.250 align:start position:0% particularly maybe during the rezoning 00:23:16.250 --> 00:23:18.760 align:start position:0% particularly maybe during the rezoning level<00:23:16.820> and<00:23:17.059> each<00:23:17.929> of<00:23:18.140> them<00:23:18.200> has<00:23:18.350> maybe<00:23:18.620> a 00:23:18.760 --> 00:23:18.770 align:start position:0% level and each of them has maybe a 00:23:18.770 --> 00:23:21.460 align:start position:0% level and each of them has maybe a different<00:23:19.040> variety<00:23:19.340> or<00:23:19.880> how<00:23:20.809> it<00:23:21.050> looks<00:23:21.350> and 00:23:21.460 --> 00:23:21.470 align:start position:0% different variety or how it looks and 00:23:21.470 --> 00:23:24.940 align:start position:0% different variety or how it looks and feels<00:23:21.650> but<00:23:22.010> i<00:23:22.070> think<00:23:22.309> this<00:23:23.170> this<00:23:24.170> concept<00:23:24.800> of 00:23:24.940 --> 00:23:24.950 align:start position:0% feels but i think this this concept of 00:23:24.950 --> 00:23:26.350 align:start position:0% feels but i think this this concept of tiered<00:23:25.190> approach<00:23:25.309> we've<00:23:25.760> looked<00:23:25.880> at<00:23:26.030> several 00:23:26.350 --> 00:23:26.360 align:start position:0% tiered approach we've looked at several 00:23:26.360 --> 00:23:28.630 align:start position:0% tiered approach we've looked at several different<00:23:26.480> options<00:23:26.920> through<00:23:27.920> a<00:23:28.130> couple 00:23:28.630 --> 00:23:28.640 align:start position:0% different options through a couple 00:23:28.640 --> 00:23:30.280 align:start position:0% different options through a couple different<00:23:28.730> work<00:23:29.059> sessions<00:23:29.540> with<00:23:29.690> the<00:23:29.780> council 00:23:30.280 --> 00:23:30.290 align:start position:0% different work sessions with the council 00:23:30.290 --> 00:23:32.620 align:start position:0% different work sessions with the council and<00:23:30.410> this<00:23:30.559> is<00:23:30.740> the<00:23:30.950> this<00:23:31.640> is<00:23:31.700> the<00:23:31.880> the<00:23:32.270> approach 00:23:32.620 --> 00:23:32.630 align:start position:0% and this is the this is the the approach 00:23:32.630 --> 00:23:34.480 align:start position:0% and this is the this is the the approach that<00:23:32.960> they<00:23:33.350> felt<00:23:33.590> most<00:23:33.800> comfortable<00:23:33.980> within 00:23:34.480 --> 00:23:34.490 align:start position:0% that they felt most comfortable within 00:23:34.490 --> 00:23:38.560 align:start position:0% that they felt most comfortable within it<00:23:34.820> that<00:23:35.000> it<00:23:35.540> at<00:23:36.020> least<00:23:37.120> resolved<00:23:38.120> a<00:23:38.210> lot<00:23:38.390> of 00:23:38.560 --> 00:23:38.570 align:start position:0% it that it at least resolved a lot of 00:23:38.570 --> 00:23:41.110 align:start position:0% it that it at least resolved a lot of their<00:23:38.809> issues<00:23:39.260> as<00:23:39.559> best<00:23:39.770> they<00:23:39.860> could<00:23:39.980> does<00:23:40.940> it 00:23:41.110 --> 00:23:41.120 align:start position:0% their issues as best they could does it 00:23:41.120 --> 00:23:43.060 align:start position:0% their issues as best they could does it isn't<00:23:41.420> the<00:23:41.480> best<00:23:41.660> of<00:23:41.840> every<00:23:42.110> world<00:23:42.350> everything 00:23:43.060 --> 00:23:43.070 align:start position:0% isn't the best of every world everything 00:23:43.070 --> 00:23:44.590 align:start position:0% isn't the best of every world everything that<00:23:43.220> we'd<00:23:43.340> like<00:23:43.490> to<00:23:43.610> have<00:23:43.760> but<00:23:44.000> it<00:23:44.090> it<00:23:44.360> comes 00:23:44.590 --> 00:23:44.600 align:start position:0% that we'd like to have but it it comes 00:23:44.600 --> 00:23:47.200 align:start position:0% that we'd like to have but it it comes close<00:23:44.900> to<00:23:44.929> what<00:23:45.260> i<00:23:45.290> believe<00:23:45.650> they<00:23:45.830> had<00:23:46.210> support 00:23:47.200 --> 00:23:47.210 align:start position:0% close to what i believe they had support 00:23:47.210 --> 00:23:53.140 align:start position:0% close to what i believe they had support for<00:23:47.420> okay<00:23:50.620> any<00:23:51.620> other<00:23:51.679> questions<00:23:52.000> your<00:23:53.000> one 00:23:53.140 --> 00:23:53.150 align:start position:0% for okay any other questions your one 00:23:53.150 --> 00:23:55.780 align:start position:0% for okay any other questions your one more<00:23:53.300> did<00:23:53.840> we<00:23:53.990> take<00:23:54.200> into<00:23:54.760> consideration<00:23:55.760> the 00:23:55.780 --> 00:23:55.790 align:start position:0% more did we take into consideration the 00:23:55.790 --> 00:23:57.490 align:start position:0% more did we take into consideration the the<00:23:56.360> street<00:23:56.780> with<00:23:57.050> because<00:23:57.320> different 00:23:57.490 --> 00:23:57.500 align:start position:0% the street with because different 00:23:57.500 --> 00:23:58.840 align:start position:0% the street with because different neighborhoods<00:23:57.950> have<00:23:58.070> different<00:23:58.460> you<00:23:58.760> know 00:23:58.840 --> 00:23:58.850 align:start position:0% neighborhoods have different you know 00:23:58.850 --> 00:24:00.070 align:start position:0% neighborhoods have different you know some<00:23:59.059> neighborhoods<00:23:59.390> you<00:23:59.480> can<00:23:59.600> park<00:23:59.840> and<00:23:59.990> have 00:24:00.070 --> 00:24:00.080 align:start position:0% some neighborhoods you can park and have 00:24:00.080 --> 00:24:01.450 align:start position:0% some neighborhoods you can park and have two<00:24:00.230> cars<00:24:00.410> passed<00:24:00.740> through<00:24:01.010> what<00:24:01.160> does<00:24:01.309> that 00:24:01.450 --> 00:24:01.460 align:start position:0% two cars passed through what does that 00:24:01.460 --> 00:24:09.010 align:start position:0% two cars passed through what does that enter<00:24:01.790> into<00:24:02.210> this<00:24:02.390> at<00:24:02.570> all<00:24:05.890> it<00:24:07.600> generally<00:24:08.600> no 00:24:09.010 --> 00:24:09.020 align:start position:0% enter into this at all it generally no 00:24:09.020 --> 00:24:11.169 align:start position:0% enter into this at all it generally no because<00:24:09.860> generally<00:24:10.220> all<00:24:10.370> our<00:24:10.550> streets<00:24:10.940> are 00:24:11.169 --> 00:24:11.179 align:start position:0% because generally all our streets are 00:24:11.179 --> 00:24:14.950 align:start position:0% because generally all our streets are designed<00:24:11.800> safely<00:24:12.800> for<00:24:12.980> a<00:24:13.010> safe<00:24:13.250> width<00:24:13.750> it<00:24:14.750> gets 00:24:14.950 --> 00:24:14.960 align:start position:0% designed safely for a safe width it gets 00:24:14.960 --> 00:24:16.780 align:start position:0% designed safely for a safe width it gets when<00:24:15.140> you<00:24:15.260> talking<00:24:15.650> about<00:24:15.800> these<00:24:16.400> older 00:24:16.780 --> 00:24:16.790 align:start position:0% when you talking about these older 00:24:16.790 --> 00:24:17.950 align:start position:0% when you talking about these older neighborhoods<00:24:17.300> that<00:24:17.480> were<00:24:17.540> built<00:24:17.780> at 00:24:17.950 --> 00:24:17.960 align:start position:0% neighborhoods that were built at 00:24:17.960 --> 00:24:20.950 align:start position:0% neighborhoods that were built at counties<00:24:18.380> division<00:24:18.980> standards<00:24:19.690> even<00:24:20.690> though 00:24:20.950 --> 00:24:20.960 align:start position:0% counties division standards even though 00:24:20.960 --> 00:24:22.660 align:start position:0% counties division standards even though they're<00:24:21.110> still<00:24:21.380> safe<00:24:21.740> with<00:24:22.040> because<00:24:22.400> they<00:24:22.610> are 00:24:22.660 --> 00:24:22.670 align:start position:0% they're still safe with because they are 00:24:22.670 --> 00:24:24.310 align:start position:0% they're still safe with because they are they<00:24:23.090> are<00:24:23.300> prescribed<00:24:23.900> by<00:24:24.080> the<00:24:24.140> north 00:24:24.310 --> 00:24:24.320 align:start position:0% they are prescribed by the north 00:24:24.320 --> 00:24:27.340 align:start position:0% they are prescribed by the north carolina<00:24:24.740> do<00:24:25.220> t<00:24:25.490> so<00:24:26.330> they're<00:24:26.510> all<00:24:26.660> safe<00:24:27.020> wits 00:24:27.340 --> 00:24:27.350 align:start position:0% carolina do t so they're all safe wits 00:24:27.350 --> 00:24:29.580 align:start position:0% carolina do t so they're all safe wits the<00:24:27.620> question<00:24:27.980> is<00:24:28.100> they<00:24:28.250> just<00:24:28.400> don't<00:24:28.610> have 00:24:29.580 --> 00:24:29.590 align:start position:0% the question is they just don't have 00:24:29.590 --> 00:24:32.380 align:start position:0% the question is they just don't have more<00:24:30.590> municipal<00:24:31.130> type<00:24:31.340> settings<00:24:31.940> where<00:24:32.210> we 00:24:32.380 --> 00:24:32.390 align:start position:0% more municipal type settings where we 00:24:32.390 --> 00:24:34.960 align:start position:0% more municipal type settings where we have<00:24:32.570> streetlights<00:24:32.900> and<00:24:33.380> sidewalks<00:24:34.130> urban 00:24:34.960 --> 00:24:34.970 align:start position:0% have streetlights and sidewalks urban 00:24:34.970 --> 00:24:36.850 align:start position:0% have streetlights and sidewalks urban gutters<00:24:35.270> and<00:24:35.390> things<00:24:35.510> like<00:24:35.660> that<00:24:35.720> so<00:24:35.929> this 00:24:36.850 --> 00:24:36.860 align:start position:0% gutters and things like that so this 00:24:36.860 --> 00:24:38.710 align:start position:0% gutters and things like that so this ordinance<00:24:37.370> really<00:24:37.610> addresses<00:24:38.179> those<00:24:38.390> very 00:24:38.710 --> 00:24:38.720 align:start position:0% ordinance really addresses those very 00:24:38.720 --> 00:24:40.870 align:start position:0% ordinance really addresses those very older<00:24:39.050> neighborhoods<00:24:39.530> where<00:24:39.770> where<00:24:40.520> we<00:24:40.700> don't 00:24:40.870 --> 00:24:40.880 align:start position:0% older neighborhoods where where we don't 00:24:40.880 --> 00:24:43.500 align:start position:0% older neighborhoods where where we don't have<00:24:41.030> similar<00:24:41.780> types<00:24:42.050> of<00:24:42.200> Street<00:24:42.500> types 00:24:43.500 --> 00:24:43.510 align:start position:0% have similar types of Street types 00:24:43.510 --> 00:24:45.730 align:start position:0% have similar types of Street types municipal<00:24:44.510> type<00:24:44.690> Street<00:24:44.990> types<00:24:45.200> with<00:24:45.440> that 00:24:45.730 --> 00:24:45.740 align:start position:0% municipal type Street types with that 00:24:45.740 --> 00:24:49.180 align:start position:0% municipal type Street types with that and<00:24:46.010> this<00:24:46.550> ordinance<00:24:46.970> goes<00:24:47.150> goes<00:24:47.720> a<00:24:48.500> ways<00:24:48.679> into 00:24:49.180 --> 00:24:49.190 align:start position:0% and this ordinance goes goes a ways into 00:24:49.190 --> 00:24:52.419 align:start position:0% and this ordinance goes goes a ways into helping<00:24:49.550> resolve<00:24:50.090> those<00:24:50.420> issues<00:24:50.480> so<00:24:51.170> that<00:24:51.429> if 00:24:52.419 --> 00:24:52.429 align:start position:0% helping resolve those issues so that if 00:24:52.429 --> 00:24:55.610 align:start position:0% helping resolve those issues so that if the<00:24:52.580> neighborhood<00:24:53.230> was<00:24:54.230> built<00:24:54.440> to<00:24:54.890> a 00:24:55.610 --> 00:24:55.620 align:start position:0% the neighborhood was built to a 00:24:55.620 --> 00:24:58.910 align:start position:0% the neighborhood was built to a maybe<00:24:55.770> a<00:24:55.860> sander<00:24:56.850> 20<00:24:57.150> 30<00:24:57.330> years<00:24:57.480> ago<00:24:57.920> there's 00:24:58.910 --> 00:24:58.920 align:start position:0% maybe a sander 20 30 years ago there's 00:24:58.920 --> 00:25:00.920 align:start position:0% maybe a sander 20 30 years ago there's provisions<00:24:59.460> in<00:24:59.730> this<00:25:00.059> tiered<00:25:00.330> approach<00:25:00.450> that 00:25:00.920 --> 00:25:00.930 align:start position:0% provisions in this tiered approach that 00:25:00.930 --> 00:25:03.020 align:start position:0% provisions in this tiered approach that would<00:25:01.110> necessarily<00:25:01.320> require<00:25:02.130> vehicular 00:25:03.020 --> 00:25:03.030 align:start position:0% would necessarily require vehicular 00:25:03.030 --> 00:25:05.450 align:start position:0% would necessarily require vehicular traffic<00:25:03.270> now<00:25:03.630> they<00:25:03.750> may<00:25:03.900> require<00:25:04.460> emergency 00:25:05.450 --> 00:25:05.460 align:start position:0% traffic now they may require emergency 00:25:05.460 --> 00:25:08.000 align:start position:0% traffic now they may require emergency access<00:25:05.970> type<00:25:06.780> of<00:25:06.960> provision<00:25:07.440> or<00:25:07.620> you<00:25:07.920> know 00:25:08.000 --> 00:25:08.010 align:start position:0% access type of provision or you know 00:25:08.010 --> 00:25:10.549 align:start position:0% access type of provision or you know sidewalk<00:25:08.550> and<00:25:08.790> pedestrian<00:25:09.780> type<00:25:09.990> connections 00:25:10.549 --> 00:25:10.559 align:start position:0% sidewalk and pedestrian type connections 00:25:10.559 --> 00:25:12.260 align:start position:0% sidewalk and pedestrian type connections but<00:25:10.770> it<00:25:10.920> wouldn't<00:25:11.309> necessarily<00:25:11.460> require<00:25:12.030> that 00:25:12.260 --> 00:25:12.270 align:start position:0% but it wouldn't necessarily require that 00:25:12.270 --> 00:25:16.220 align:start position:0% but it wouldn't necessarily require that vehicular<00:25:12.920> movement<00:25:14.690> interaction<00:25:15.690> okay 00:25:16.220 --> 00:25:16.230 align:start position:0% vehicular movement interaction okay 00:25:16.230 --> 00:25:17.570 align:start position:0% vehicular movement interaction okay because<00:25:16.680> one<00:25:16.860> of<00:25:16.890> the<00:25:17.010> things<00:25:17.070> we're<00:25:17.340> noticing 00:25:17.570 --> 00:25:17.580 align:start position:0% because one of the things we're noticing 00:25:17.580 --> 00:25:19.340 align:start position:0% because one of the things we're noticing is<00:25:17.880> the<00:25:18.120> parking<00:25:18.540> on<00:25:18.690> the<00:25:18.780> side<00:25:18.960> of<00:25:19.020> the<00:25:19.170> road 00:25:19.340 --> 00:25:19.350 align:start position:0% is the parking on the side of the road 00:25:19.350 --> 00:25:21.260 align:start position:0% is the parking on the side of the road really<00:25:19.890> limits<00:25:20.280> how<00:25:20.430> much<00:25:20.490> traffic<00:25:21.000> you<00:25:21.240> can 00:25:21.260 --> 00:25:21.270 align:start position:0% really limits how much traffic you can 00:25:21.270 --> 00:25:24.290 align:start position:0% really limits how much traffic you can put<00:25:21.600> on<00:25:21.690> that<00:25:21.840> road<00:25:22.020> to<00:25:22.260> right<00:25:22.770> so<00:25:23.340> right<00:25:23.760> it 00:25:24.290 --> 00:25:24.300 align:start position:0% put on that road to right so right it 00:25:24.300 --> 00:25:26.180 align:start position:0% put on that road to right so right it generally<00:25:24.809> the<00:25:24.990> subdivision<00:25:25.470> standards<00:25:26.070> by 00:25:26.180 --> 00:25:26.190 align:start position:0% generally the subdivision standards by 00:25:26.190 --> 00:25:27.830 align:start position:0% generally the subdivision standards by North<00:25:26.520> Carolina<00:25:26.910> deity<00:25:27.240> they<00:25:27.420> were<00:25:27.480> designed 00:25:27.830 --> 00:25:27.840 align:start position:0% North Carolina deity they were designed 00:25:27.840 --> 00:25:30.110 align:start position:0% North Carolina deity they were designed for<00:25:27.990> for<00:25:28.530> subdivision<00:25:29.100> roads<00:25:29.370> of<00:25:29.700> you<00:25:30.000> know 00:25:30.110 --> 00:25:30.120 align:start position:0% for for subdivision roads of you know 00:25:30.120 --> 00:25:33.440 align:start position:0% for for subdivision roads of you know daily<00:25:31.050> traffic<00:25:31.290> volumes<00:25:31.830> of<00:25:32.070> you<00:25:32.340> know<00:25:32.460> 300<00:25:33.360> to 00:25:33.440 --> 00:25:33.450 align:start position:0% daily traffic volumes of you know 300 to 00:25:33.450 --> 00:25:39.350 align:start position:0% daily traffic volumes of you know 300 to 500<00:25:34.190> cars<00:25:35.190> a<00:25:35.309> day<00:25:36.140> so<00:25:37.760> that<00:25:38.760> that<00:25:39.059> helps<00:25:39.179> you 00:25:39.350 --> 00:25:39.360 align:start position:0% 500 cars a day so that that helps you 00:25:39.360 --> 00:25:46.760 align:start position:0% 500 cars a day so that that helps you out<00:25:39.390> though<00:25:41.750> yes<00:25:43.040> mr.<00:25:44.040> Johnson<00:25:45.500> how<00:25:46.500> many 00:25:46.760 --> 00:25:46.770 align:start position:0% out though yes mr. Johnson how many 00:25:46.770 --> 00:25:51.230 align:start position:0% out though yes mr. Johnson how many people<00:25:47.610> attended<00:25:48.270> public<00:25:49.230> hearings<00:25:50.240> for 00:25:51.230 --> 00:25:51.240 align:start position:0% people attended public hearings for 00:25:51.240 --> 00:25:53.450 align:start position:0% people attended public hearings for these<00:25:51.420> two<00:25:51.929> issues<00:25:52.140> I<00:25:52.620> assume<00:25:53.040> you<00:25:53.280> were 00:25:53.450 --> 00:25:53.460 align:start position:0% these two issues I assume you were 00:25:53.460 --> 00:25:57.470 align:start position:0% these two issues I assume you were participant<00:25:55.520> yeah<00:25:56.520> I<00:25:56.550> don't<00:25:56.670> I<00:25:56.910> didn't<00:25:57.240> don't 00:25:57.470 --> 00:25:57.480 align:start position:0% participant yeah I don't I didn't don't 00:25:57.480 --> 00:26:00.919 align:start position:0% participant yeah I don't I didn't don't remember<00:25:57.900> there<00:25:58.080> was<00:25:58.230> a<00:25:58.290> lot<00:25:58.620> of<00:25:59.929> interaction 00:26:00.919 --> 00:26:00.929 align:start position:0% remember there was a lot of interaction 00:26:00.929 --> 00:26:02.510 align:start position:0% remember there was a lot of interaction from<00:26:01.110> the<00:26:01.260> public<00:26:01.620> that<00:26:01.920> was<00:26:02.130> given<00:26:02.429> to 00:26:02.510 --> 00:26:02.520 align:start position:0% from the public that was given to 00:26:02.520 --> 00:26:06.110 align:start position:0% from the public that was given to opportunities<00:26:03.360> for<00:26:04.190> for<00:26:05.190> feedback<00:26:05.400> at<00:26:05.790> public 00:26:06.110 --> 00:26:06.120 align:start position:0% opportunities for for feedback at public 00:26:06.120 --> 00:26:09.560 align:start position:0% opportunities for for feedback at public hearings<00:26:07.040> we<00:26:08.040> also<00:26:08.250> the<00:26:09.240> planning<00:26:09.540> department 00:26:09.560 --> 00:26:09.570 align:start position:0% hearings we also the planning department 00:26:09.570 --> 00:26:13.450 align:start position:0% hearings we also the planning department sent<00:26:10.140> out<00:26:10.320> a<00:26:10.400> kind<00:26:11.400> of<00:26:11.490> a<00:26:11.580> listing<00:26:12.120> to<00:26:13.050> their 00:26:13.450 --> 00:26:13.460 align:start position:0% sent out a kind of a listing to their 00:26:13.460 --> 00:26:16.190 align:start position:0% sent out a kind of a listing to their normal<00:26:14.460> developer<00:26:15.120> groups<00:26:15.330> prior<00:26:15.660> to<00:26:15.960> the 00:26:16.190 --> 00:26:16.200 align:start position:0% normal developer groups prior to the 00:26:16.200 --> 00:26:18.190 align:start position:0% normal developer groups prior to the public<00:26:17.130> hearing<00:26:17.250> that<00:26:17.520> went<00:26:17.730> in<00:26:17.820> March 00:26:18.190 --> 00:26:18.200 align:start position:0% public hearing that went in March 00:26:18.200 --> 00:26:20.270 align:start position:0% public hearing that went in March advising<00:26:19.200> them<00:26:19.320> that<00:26:19.530> we<00:26:19.679> were<00:26:19.830> planning<00:26:20.130> to 00:26:20.270 --> 00:26:20.280 align:start position:0% advising them that we were planning to 00:26:20.280 --> 00:26:23.240 align:start position:0% advising them that we were planning to to<00:26:20.700> come<00:26:20.880> forward<00:26:21.500> they're<00:26:22.500> invited<00:26:22.980> that<00:26:23.130> if 00:26:23.240 --> 00:26:23.250 align:start position:0% to come forward they're invited that if 00:26:23.250 --> 00:26:24.470 align:start position:0% to come forward they're invited that if they<00:26:23.370> had<00:26:23.490> any<00:26:23.610> commentary<00:26:24.030> before<00:26:24.360> that 00:26:24.470 --> 00:26:24.480 align:start position:0% they had any commentary before that 00:26:24.480 --> 00:26:25.669 align:start position:0% they had any commentary before that meaning<00:26:24.750> they<00:26:24.840> certainly<00:26:25.170> could<00:26:25.380> meet<00:26:25.530> with 00:26:25.669 --> 00:26:25.679 align:start position:0% meaning they certainly could meet with 00:26:25.679 --> 00:26:27.500 align:start position:0% meaning they certainly could meet with staff<00:26:25.890> to<00:26:26.160> talk<00:26:26.370> about<00:26:26.550> particularly 00:26:27.500 --> 00:26:27.510 align:start position:0% staff to talk about particularly 00:26:27.510 --> 00:26:29.930 align:start position:0% staff to talk about particularly connectivity<00:26:28.190> so<00:26:29.190> there<00:26:29.370> has<00:26:29.460> been<00:26:29.670> some 00:26:29.930 --> 00:26:29.940 align:start position:0% connectivity so there has been some 00:26:29.940 --> 00:26:31.820 align:start position:0% connectivity so there has been some opportunities<00:26:30.780> for<00:26:30.990> public<00:26:31.110> feedback<00:26:31.410> but<00:26:31.770> I 00:26:31.820 --> 00:26:31.830 align:start position:0% opportunities for public feedback but I 00:26:31.830 --> 00:26:33.110 align:start position:0% opportunities for public feedback but I don't<00:26:31.980> remember<00:26:32.100> there<00:26:32.400> being<00:26:32.429> a<00:26:32.730> lot<00:26:32.760> of 00:26:33.110 --> 00:26:33.120 align:start position:0% don't remember there being a lot of 00:26:33.120 --> 00:26:35.060 align:start position:0% don't remember there being a lot of feedback<00:26:33.690> in<00:26:34.020> fact<00:26:34.200> we<00:26:34.320> didn't<00:26:34.530> really<00:26:34.770> hear<00:26:35.010> a 00:26:35.060 --> 00:26:35.070 align:start position:0% feedback in fact we didn't really hear a 00:26:35.070 --> 00:26:36.860 align:start position:0% feedback in fact we didn't really hear a lot<00:26:35.309> of<00:26:35.460> feedback<00:26:35.640> out<00:26:36.059> of<00:26:36.150> the<00:26:36.240> Wake<00:26:36.840> County 00:26:36.860 --> 00:26:36.870 align:start position:0% lot of feedback out of the Wake County 00:26:36.870 --> 00:26:38.660 align:start position:0% lot of feedback out of the Wake County home<00:26:37.290> builders<00:26:37.620> association<00:26:37.950> even<00:26:38.580> though 00:26:38.660 --> 00:26:38.670 align:start position:0% home builders association even though 00:26:38.670 --> 00:26:40.580 align:start position:0% home builders association even though they<00:26:38.820> were<00:26:39.020> following<00:26:40.020> and<00:26:40.140> I<00:26:40.200> know<00:26:40.260> they<00:26:40.530> did 00:26:40.580 --> 00:26:40.590 align:start position:0% they were following and I know they did 00:26:40.590 --> 00:26:43.640 align:start position:0% they were following and I know they did attend<00:26:41.720> some<00:26:42.720> of<00:26:42.750> those<00:26:42.870> work<00:26:43.050> sessions<00:26:43.500> that 00:26:43.640 --> 00:26:43.650 align:start position:0% attend some of those work sessions that 00:26:43.650 --> 00:26:45.380 align:start position:0% attend some of those work sessions that were<00:26:43.770> held<00:26:43.950> with<00:26:44.010> counsel<00:26:44.520> what<00:26:45.030> about<00:26:45.240> the 00:26:45.380 --> 00:26:45.390 align:start position:0% were held with counsel what about the 00:26:45.390 --> 00:26:47.720 align:start position:0% were held with counsel what about the developer<00:26:45.929> feedback<00:26:46.170> I<00:26:46.920> haven't<00:26:47.160> received<00:26:47.490> I 00:26:47.720 --> 00:26:47.730 align:start position:0% developer feedback I haven't received I 00:26:47.730 --> 00:26:53.360 align:start position:0% developer feedback I haven't received I haven't<00:26:48.300> received<00:26:48.690> any<00:26:48.870> specific<00:26:49.410> on<00:26:50.340> it 00:26:53.360 --> 00:26:53.370 align:start position:0% 00:26:53.370 --> 00:26:58.560 align:start position:0% any<00:26:54.370> other<00:26:54.520> questions<00:26:57.300> all<00:26:58.300> right<00:26:58.420> I'll<00:26:58.540> just 00:26:58.560 --> 00:26:58.570 align:start position:0% any other questions all right I'll just 00:26:58.570 --> 00:27:02.520 align:start position:0% any other questions all right I'll just ask<00:26:58.810> one<00:26:59.080> about<00:27:00.120> implementation<00:27:01.120> so<00:27:01.870> someone 00:27:02.520 --> 00:27:02.530 align:start position:0% ask one about implementation so someone 00:27:02.530 --> 00:27:05.100 align:start position:0% ask one about implementation so someone is<00:27:02.560> going<00:27:03.280> to<00:27:03.370> include<00:27:03.700> a<00:27:04.030> connectivity<00:27:04.870> issue 00:27:05.100 --> 00:27:05.110 align:start position:0% is going to include a connectivity issue 00:27:05.110 --> 00:27:08.220 align:start position:0% is going to include a connectivity issue in<00:27:05.530> their<00:27:05.680> zoning<00:27:05.950> condition<00:27:06.610> they<00:27:07.570> first<00:27:07.900> get 00:27:08.220 --> 00:27:08.230 align:start position:0% in their zoning condition they first get 00:27:08.230 --> 00:27:12.030 align:start position:0% in their zoning condition they first get a<00:27:08.520> ruling<00:27:09.520> so<00:27:09.880> to<00:27:09.940> speak<00:27:10.300> from<00:27:10.780> staff<00:27:11.500> as<00:27:11.830> to 00:27:12.030 --> 00:27:12.040 align:start position:0% a ruling so to speak from staff as to 00:27:12.040 --> 00:27:15.480 align:start position:0% a ruling so to speak from staff as to what<00:27:12.340> tier<00:27:12.790> that<00:27:13.390> area<00:27:13.720> would<00:27:13.870> be<00:27:13.930> in<00:27:14.490> yes 00:27:15.480 --> 00:27:15.490 align:start position:0% what tier that area would be in yes 00:27:15.490 --> 00:27:17.550 align:start position:0% what tier that area would be in yes there<00:27:15.790> would<00:27:15.910> need<00:27:16.090> to<00:27:16.150> be<00:27:16.330> a<00:27:16.870> determination 00:27:17.550 --> 00:27:17.560 align:start position:0% there would need to be a determination 00:27:17.560 --> 00:27:19.740 align:start position:0% there would need to be a determination could<00:27:17.860> be<00:27:18.010> made<00:27:18.220> at<00:27:18.550> the<00:27:18.880> time<00:27:19.150> of<00:27:19.660> the 00:27:19.740 --> 00:27:19.750 align:start position:0% could be made at the time of the 00:27:19.750 --> 00:27:22.800 align:start position:0% could be made at the time of the rezoning<00:27:20.170> for<00:27:20.560> what<00:27:20.770> the<00:27:21.040> Pyramid<00:27:21.670> of<00:27:22.210> the 00:27:22.800 --> 00:27:22.810 align:start position:0% rezoning for what the Pyramid of the 00:27:22.810 --> 00:27:24.540 align:start position:0% rezoning for what the Pyramid of the tier<00:27:23.080> of<00:27:23.200> the<00:27:23.320> adjacent<00:27:23.560> neighborhood<00:27:24.280> and 00:27:24.540 --> 00:27:24.550 align:start position:0% tier of the adjacent neighborhood and 00:27:24.550 --> 00:27:29.400 align:start position:0% tier of the adjacent neighborhood and then<00:27:25.330> that<00:27:25.540> would<00:27:26.220> establish<00:27:27.930> you<00:27:28.930> know<00:27:29.050> the 00:27:29.400 --> 00:27:29.410 align:start position:0% then that would establish you know the 00:27:29.410 --> 00:27:31.950 align:start position:0% then that would establish you know the range<00:27:30.310> of<00:27:30.550> zoning<00:27:30.970> conditions<00:27:31.510> it<00:27:31.720> could<00:27:31.840> at 00:27:31.950 --> 00:27:31.960 align:start position:0% range of zoning conditions it could at 00:27:31.960 --> 00:27:34.170 align:start position:0% range of zoning conditions it could at least<00:27:32.080> be<00:27:32.280> considered<00:27:33.280> based<00:27:33.490> on<00:27:33.670> that<00:27:33.820> tier 00:27:34.170 --> 00:27:34.180 align:start position:0% least be considered based on that tier 00:27:34.180 --> 00:27:38.100 align:start position:0% least be considered based on that tier so<00:27:34.960> that<00:27:35.170> would<00:27:35.350> remain<00:27:35.980> the<00:27:36.250> town's<00:27:36.720> call<00:27:37.720> it 00:27:38.100 --> 00:27:38.110 align:start position:0% so that would remain the town's call it 00:27:38.110 --> 00:27:40.260 align:start position:0% so that would remain the town's call it would<00:27:38.290> not<00:27:38.470> be<00:27:38.680> someone<00:27:39.520> could<00:27:39.670> apply<00:27:39.910> and<00:27:40.150> say 00:27:40.260 --> 00:27:40.270 align:start position:0% would not be someone could apply and say 00:27:40.270 --> 00:27:43.080 align:start position:0% would not be someone could apply and say I'm<00:27:40.840> applying<00:27:41.380> to<00:27:41.650> be<00:27:41.770> tier<00:27:42.040> 2<00:27:42.280> here<00:27:42.550> based<00:27:42.820> on 00:27:43.080 --> 00:27:43.090 align:start position:0% I'm applying to be tier 2 here based on 00:27:43.090 --> 00:27:45.180 align:start position:0% I'm applying to be tier 2 here based on XYZ<00:27:43.780> correct<00:27:44.200> no<00:27:44.410> you<00:27:44.470> don't<00:27:44.710> you<00:27:44.980> wouldn't 00:27:45.180 --> 00:27:45.190 align:start position:0% XYZ correct no you don't you wouldn't 00:27:45.190 --> 00:27:49.830 align:start position:0% XYZ correct no you don't you wouldn't apply<00:27:45.490> to<00:27:45.640> be<00:27:46.030> a<00:27:46.060> tier<00:27:46.450> I<00:27:46.480> mean<00:27:47.200> if<00:27:47.440> the<00:27:48.840> the 00:27:49.830 --> 00:27:49.840 align:start position:0% apply to be a tier I mean if the the 00:27:49.840 --> 00:27:52.320 align:start position:0% apply to be a tier I mean if the the applicant<00:27:50.470> for<00:27:50.800> the<00:27:51.190> subdivision<00:27:52.000> that<00:27:52.120> was 00:27:52.320 --> 00:27:52.330 align:start position:0% applicant for the subdivision that was 00:27:52.330 --> 00:27:55.350 align:start position:0% applicant for the subdivision that was proposed<00:27:52.870> would<00:27:53.620> be<00:27:54.220> adjacent<00:27:54.820> to<00:27:55.330> a 00:27:55.350 --> 00:27:55.360 align:start position:0% proposed would be adjacent to a 00:27:55.360 --> 00:27:57.630 align:start position:0% proposed would be adjacent to a neighborhood<00:27:55.900> I<00:27:56.290> mean<00:27:56.530> presumably<00:27:56.710> in<00:27:57.370> order 00:27:57.630 --> 00:27:57.640 align:start position:0% neighborhood I mean presumably in order 00:27:57.640 --> 00:27:59.210 align:start position:0% neighborhood I mean presumably in order for<00:27:57.820> the<00:27:57.880> issue<00:27:58.060> to<00:27:58.330> come<00:27:58.540> up<00:27:58.720> there<00:27:58.930> would<00:27:59.080> be 00:27:59.210 --> 00:27:59.220 align:start position:0% for the issue to come up there would be 00:27:59.220 --> 00:28:01.880 align:start position:0% for the issue to come up there would be you<00:28:00.220> know<00:28:00.370> some<00:28:00.640> question<00:28:01.180> of<00:28:01.420> the 00:28:01.880 --> 00:28:01.890 align:start position:0% you know some question of the 00:28:01.890 --> 00:28:05.340 align:start position:0% you know some question of the connectivity<00:28:02.890> requirements<00:28:03.900> and<00:28:04.900> then<00:28:05.230> we 00:28:05.340 --> 00:28:05.350 align:start position:0% connectivity requirements and then we 00:28:05.350 --> 00:28:07.170 align:start position:0% connectivity requirements and then we would<00:28:05.500> be<00:28:05.650> looking<00:28:05.830> at<00:28:06.160> the<00:28:06.400> whatever<00:28:07.090> the 00:28:07.170 --> 00:28:07.180 align:start position:0% would be looking at the whatever the 00:28:07.180 --> 00:28:08.910 align:start position:0% would be looking at the whatever the adjacent<00:28:07.810> neighborhood<00:28:08.200> is<00:28:08.380> to<00:28:08.590> determine 00:28:08.910 --> 00:28:08.920 align:start position:0% adjacent neighborhood is to determine 00:28:08.920 --> 00:28:10.710 align:start position:0% adjacent neighborhood is to determine what<00:28:09.550> the<00:28:09.700> tier<00:28:09.910> of<00:28:10.030> that<00:28:10.180> neighborhood<00:28:10.390> is 00:28:10.710 --> 00:28:10.720 align:start position:0% what the tier of that neighborhood is 00:28:10.720 --> 00:28:13.410 align:start position:0% what the tier of that neighborhood is based<00:28:11.080> on<00:28:11.290> those<00:28:11.470> criteria<00:28:12.160> and<00:28:12.460> then<00:28:13.090> once 00:28:13.410 --> 00:28:13.420 align:start position:0% based on those criteria and then once 00:28:13.420 --> 00:28:17.310 align:start position:0% based on those criteria and then once the<00:28:13.690> tier<00:28:13.960> was<00:28:14.140> determined<00:28:14.830> there<00:28:15.460> are<00:28:16.320> you 00:28:17.310 --> 00:28:17.320 align:start position:0% the tier was determined there are you 00:28:17.320 --> 00:28:19.710 align:start position:0% the tier was determined there are you know<00:28:17.470> several<00:28:17.940> you<00:28:18.940> know<00:28:19.060> several<00:28:19.390> options 00:28:19.710 --> 00:28:19.720 align:start position:0% know several you know several options 00:28:19.720 --> 00:28:21.810 align:start position:0% know several you know several options that<00:28:20.200> you<00:28:20.380> can<00:28:20.410> see<00:28:20.860> you<00:28:21.250> know<00:28:21.340> kind<00:28:21.580> of<00:28:21.700> in 00:28:21.810 --> 00:28:21.820 align:start position:0% that you can see you know kind of in 00:28:21.820 --> 00:28:24.390 align:start position:0% that you can see you know kind of in this<00:28:21.940> table<00:28:22.240> with<00:28:22.690> with<00:28:23.440> what<00:28:23.680> could<00:28:23.950> or<00:28:24.190> could 00:28:24.390 --> 00:28:24.400 align:start position:0% this table with with what could or could 00:28:24.400 --> 00:28:26.490 align:start position:0% this table with with what could or could not<00:28:24.430> be<00:28:24.850> allowed<00:28:25.270> as<00:28:25.510> a<00:28:25.540> zoning<00:28:25.990> condition 00:28:26.490 --> 00:28:26.500 align:start position:0% not be allowed as a zoning condition 00:28:26.500 --> 00:28:29.600 align:start position:0% not be allowed as a zoning condition based<00:28:26.860> on<00:28:27.130> based<00:28:27.850> on<00:28:28.120> the<00:28:28.240> tier<00:28:28.510> because<00:28:28.990> again 00:28:29.600 --> 00:28:29.610 align:start position:0% based on based on the tier because again 00:28:29.610 --> 00:28:32.250 align:start position:0% based on based on the tier because again whatever<00:28:30.610> is<00:28:31.090> allowed<00:28:31.480> with<00:28:31.720> the<00:28:31.750> tier<00:28:32.050> you've 00:28:32.250 --> 00:28:32.260 align:start position:0% whatever is allowed with the tier you've 00:28:32.260 --> 00:28:34.110 align:start position:0% whatever is allowed with the tier you've got<00:28:32.470> to<00:28:32.740> you<00:28:33.010> could<00:28:33.190> only<00:28:33.370> have<00:28:33.640> a<00:28:33.670> zoning 00:28:34.110 --> 00:28:34.120 align:start position:0% got to you could only have a zoning 00:28:34.120 --> 00:28:37.910 align:start position:0% got to you could only have a zoning condition<00:28:34.630> that<00:28:34.810> made<00:28:35.020> it<00:28:35.200> more<00:28:36.360> restrictive 00:28:37.910 --> 00:28:37.920 align:start position:0% condition that made it more restrictive 00:28:37.920 --> 00:28:41.400 align:start position:0% condition that made it more restrictive the<00:28:38.920> reason<00:28:39.160> I<00:28:39.250> ask<00:28:39.400> Aly<00:28:39.610> to<00:28:39.700> use<00:28:39.970> some<00:28:40.240> the<00:28:41.140> one 00:28:41.400 --> 00:28:41.410 align:start position:0% the reason I ask Aly to use some the one 00:28:41.410 --> 00:28:45.090 align:start position:0% the reason I ask Aly to use some the one condition<00:28:41.770> about<00:28:42.730> a<00:28:43.440> right-of-way<00:28:44.440> may<00:28:44.800> exist 00:28:45.090 --> 00:28:45.100 align:start position:0% condition about a right-of-way may exist 00:28:45.100 --> 00:28:47.670 align:start position:0% condition about a right-of-way may exist to<00:28:45.250> the<00:28:45.340> common<00:28:45.670> property<00:28:46.120> line<00:28:46.330> but<00:28:47.290> a<00:28:47.320> street 00:28:47.670 --> 00:28:47.680 align:start position:0% to the common property line but a street 00:28:47.680 --> 00:28:50.700 align:start position:0% to the common property line but a street may<00:28:47.770> not<00:28:47.920> may<00:28:48.250> not<00:28:48.430> be<00:28:48.640> there<00:28:48.820> is<00:28:49.390> that<00:28:49.750> sort<00:28:50.590> of 00:28:50.700 --> 00:28:50.710 align:start position:0% may not may not be there is that sort of 00:28:50.710 --> 00:28:52.950 align:start position:0% may not may not be there is that sort of a<00:28:50.830> fluid<00:28:51.640> thing<00:28:51.670> or<00:28:52.060> is<00:28:52.150> there<00:28:52.300> a<00:28:52.330> bright<00:28:52.720> line 00:28:52.950 --> 00:28:52.960 align:start position:0% a fluid thing or is there a bright line 00:28:52.960 --> 00:28:55.500 align:start position:0% a fluid thing or is there a bright line where<00:28:53.200> you're<00:28:53.380> either<00:28:53.530> your<00:28:54.430> road<00:28:54.670> is<00:28:54.850> up<00:28:55.210> to 00:28:55.500 --> 00:28:55.510 align:start position:0% where you're either your road is up to 00:28:55.510 --> 00:28:57.240 align:start position:0% where you're either your road is up to the<00:28:55.660> common<00:28:56.170> property<00:28:56.560> line<00:28:56.710> or<00:28:56.860> it's<00:28:57.010> not 00:28:57.240 --> 00:28:57.250 align:start position:0% the common property line or it's not 00:28:57.250 --> 00:28:59.490 align:start position:0% the common property line or it's not because<00:28:57.580> I<00:28:57.640> know<00:28:57.940> some<00:28:58.390> stub<00:28:58.840> areas<00:28:59.260> have 00:28:59.490 --> 00:28:59.500 align:start position:0% because I know some stub areas have 00:28:59.500 --> 00:29:02.100 align:start position:0% because I know some stub areas have maybe<00:29:00.190> a<00:29:00.310> patch<00:29:00.610> of<00:29:00.640> gravel<00:29:01.210> with<00:29:01.660> some<00:29:01.870> weeds 00:29:02.100 --> 00:29:02.110 align:start position:0% maybe a patch of gravel with some weeds 00:29:02.110 --> 00:29:04.409 align:start position:0% maybe a patch of gravel with some weeds grown<00:29:02.500> in<00:29:02.710> it<00:29:02.860> and<00:29:03.160> do<00:29:03.280> they<00:29:03.400> say<00:29:03.670> that<00:29:03.850> that 00:29:04.409 --> 00:29:04.419 align:start position:0% grown in it and do they say that that 00:29:04.419 --> 00:29:07.710 align:start position:0% grown in it and do they say that that I<00:29:04.539> mean<00:29:05.080> I<00:29:05.139> think<00:29:05.409> in<00:29:05.559> some<00:29:05.590> cases<00:29:06.129> there<00:29:06.850> it 00:29:07.710 --> 00:29:07.720 align:start position:0% I mean I think in some cases there it 00:29:07.720 --> 00:29:10.109 align:start position:0% I mean I think in some cases there it mean<00:29:08.109> when<00:29:08.470> the<00:29:08.590> initial<00:29:08.830> subdivision<00:29:09.759> was 00:29:10.109 --> 00:29:10.119 align:start position:0% mean when the initial subdivision was 00:29:10.119 --> 00:29:12.389 align:start position:0% mean when the initial subdivision was done<00:29:10.570> it<00:29:10.809> may<00:29:10.960> not<00:29:11.139> have<00:29:11.320> been<00:29:11.350> feasible<00:29:11.679> to<00:29:12.070> go 00:29:12.389 --> 00:29:12.399 align:start position:0% done it may not have been feasible to go 00:29:12.399 --> 00:29:16.590 align:start position:0% done it may not have been feasible to go exactly<00:29:13.359> up<00:29:13.720> to<00:29:13.749> the<00:29:13.960> property<00:29:14.409> line<00:29:15.239> but<00:29:16.239> yet 00:29:16.590 --> 00:29:16.600 align:start position:0% exactly up to the property line but yet 00:29:16.600 --> 00:29:18.690 align:start position:0% exactly up to the property line but yet the<00:29:16.869> intent<00:29:17.289> if<00:29:17.559> the<00:29:17.799> intent<00:29:18.159> was<00:29:18.249> clearly 00:29:18.690 --> 00:29:18.700 align:start position:0% the intent if the intent was clearly 00:29:18.700 --> 00:29:21.029 align:start position:0% the intent if the intent was clearly there<00:29:18.909> for<00:29:19.210> you<00:29:19.899> know<00:29:20.019> for<00:29:20.230> that<00:29:20.320> to<00:29:20.559> open<00:29:20.889> and 00:29:21.029 --> 00:29:21.039 align:start position:0% there for you know for that to open and 00:29:21.039 --> 00:29:25.019 align:start position:0% there for you know for that to open and it's<00:29:21.659> physically<00:29:23.070> feasible<00:29:24.070> to<00:29:24.129> do<00:29:24.519> that<00:29:24.759> I 00:29:25.019 --> 00:29:25.029 align:start position:0% it's physically feasible to do that I 00:29:25.029 --> 00:29:27.509 align:start position:0% it's physically feasible to do that I mean<00:29:25.269> sometimes<00:29:25.749> debate<00:29:26.470> based<00:29:26.739> on<00:29:27.100> you<00:29:27.369> may 00:29:27.509 --> 00:29:27.519 align:start position:0% mean sometimes debate based on you may 00:29:27.519 --> 00:29:30.210 align:start position:0% mean sometimes debate based on you may need<00:29:27.700> construction<00:29:28.389> easement<00:29:28.570> sir<00:29:29.049> or<00:29:29.919> things 00:29:30.210 --> 00:29:30.220 align:start position:0% need construction easement sir or things 00:29:30.220 --> 00:29:32.460 align:start position:0% need construction easement sir or things of<00:29:30.369> that<00:29:30.429> nature<00:29:30.549> that<00:29:31.269> that<00:29:31.779> aren't<00:29:32.109> in<00:29:32.200> place 00:29:32.460 --> 00:29:32.470 align:start position:0% of that nature that that aren't in place 00:29:32.470 --> 00:29:36.029 align:start position:0% of that nature that that aren't in place initially<00:29:33.340> that<00:29:33.820> boat<00:29:34.600> I<00:29:34.899> think<00:29:35.590> if<00:29:35.769> the 00:29:36.029 --> 00:29:36.039 align:start position:0% initially that boat I think if the 00:29:36.039 --> 00:29:38.039 align:start position:0% initially that boat I think if the particularly<00:29:36.730> where<00:29:36.879> the<00:29:36.970> subdivision<00:29:37.749> was 00:29:38.039 --> 00:29:38.049 align:start position:0% particularly where the subdivision was 00:29:38.049 --> 00:29:42.499 align:start position:0% particularly where the subdivision was created<00:29:38.769> after<00:29:39.720> 1999<00:29:40.859> if<00:29:41.859> there's<00:29:42.249> a 00:29:42.499 --> 00:29:42.509 align:start position:0% created after 1999 if there's a 00:29:42.509 --> 00:29:45.299 align:start position:0% created after 1999 if there's a right-of-way<00:29:43.590> stubbing<00:29:44.590> to<00:29:44.739> the<00:29:44.859> property 00:29:45.299 --> 00:29:45.309 align:start position:0% right-of-way stubbing to the property 00:29:45.309 --> 00:29:48.539 align:start position:0% right-of-way stubbing to the property line<00:29:46.019> even<00:29:47.019> if<00:29:47.169> the<00:29:47.350> road<00:29:47.529> is<00:29:47.559> a<00:29:48.070> little<00:29:48.369> bit 00:29:48.539 --> 00:29:48.549 align:start position:0% line even if the road is a little bit 00:29:48.549 --> 00:29:50.820 align:start position:0% line even if the road is a little bit short<00:29:48.879> if<00:29:49.090> it<00:29:49.269> you<00:29:49.989> know<00:29:50.109> didn't<00:29:50.470> go<00:29:50.590> exactly 00:29:50.820 --> 00:29:50.830 align:start position:0% short if it you know didn't go exactly 00:29:50.830 --> 00:29:54.739 align:start position:0% short if it you know didn't go exactly to<00:29:51.340> the<00:29:51.489> line<00:29:51.789> then<00:29:52.720> it's<00:29:53.230> just<00:29:53.559> a<00:29:53.739> matter<00:29:53.769> of 00:29:54.739 --> 00:29:54.749 align:start position:0% to the line then it's just a matter of 00:29:54.749 --> 00:29:59.909 align:start position:0% to the line then it's just a matter of construction<00:29:56.009> issues<00:29:57.009> to<00:29:58.109> to<00:29:59.109> make<00:29:59.289> that<00:29:59.559> that 00:29:59.909 --> 00:29:59.919 align:start position:0% construction issues to to make that that 00:29:59.919 --> 00:30:02.190 align:start position:0% construction issues to to make that that final<00:30:00.369> connection<00:30:00.970> where<00:30:01.600> you<00:30:01.720> can<00:30:01.929> grade 00:30:02.190 --> 00:30:02.200 align:start position:0% final connection where you can grade 00:30:02.200 --> 00:30:03.960 align:start position:0% final connection where you can grade everything<00:30:02.710> where<00:30:02.950> the<00:30:03.340> roads<00:30:03.580> come<00:30:03.820> together 00:30:03.960 --> 00:30:03.970 align:start position:0% everything where the roads come together 00:30:03.970 --> 00:30:07.560 align:start position:0% everything where the roads come together nicely<00:30:05.249> thank<00:30:06.249> you<00:30:06.369> I<00:30:06.549> am<00:30:06.820> one<00:30:07.269> more<00:30:07.419> question 00:30:07.560 --> 00:30:07.570 align:start position:0% nicely thank you I am one more question 00:30:07.570 --> 00:30:10.560 align:start position:0% nicely thank you I am one more question just<00:30:08.019> popped<00:30:08.080> to<00:30:08.440> mind<00:30:08.470> we<00:30:09.460> received<00:30:09.909> a<00:30:10.149> note 00:30:10.560 --> 00:30:10.570 align:start position:0% just popped to mind we received a note 00:30:10.570 --> 00:30:14.430 align:start position:0% just popped to mind we received a note or<00:30:10.720> two<00:30:10.899> about<00:30:12.299> you<00:30:13.299> know<00:30:13.419> the<00:30:13.450> connectivity 00:30:14.430 --> 00:30:14.440 align:start position:0% or two about you know the connectivity 00:30:14.440 --> 00:30:16.739 align:start position:0% or two about you know the connectivity with<00:30:14.649> regard<00:30:15.070> to<00:30:15.190> like<00:30:15.700> a<00:30:15.730> shopping<00:30:16.269> center 00:30:16.739 --> 00:30:16.749 align:start position:0% with regard to like a shopping center 00:30:16.749 --> 00:30:18.690 align:start position:0% with regard to like a shopping center next<00:30:16.899> to<00:30:17.109> a<00:30:17.200> neighborhood<00:30:17.529> this<00:30:18.279> is<00:30:18.460> only 00:30:18.690 --> 00:30:18.700 align:start position:0% next to a neighborhood this is only 00:30:18.700 --> 00:30:20.669 align:start position:0% next to a neighborhood this is only neighborhood<00:30:19.330> to<00:30:19.480> neighborhood<00:30:19.509> right<00:30:20.230> is 00:30:20.669 --> 00:30:20.679 align:start position:0% neighborhood to neighborhood right is 00:30:20.679 --> 00:30:22.830 align:start position:0% neighborhood to neighborhood right is that<00:30:20.919> the<00:30:21.039> only<00:30:21.129> thing<00:30:21.309> this<00:30:21.549> addresses<00:30:22.179> well 00:30:22.830 --> 00:30:22.840 align:start position:0% that the only thing this addresses well 00:30:22.840 --> 00:30:27.269 align:start position:0% that the only thing this addresses well this<00:30:23.109> is<00:30:24.509> this<00:30:25.509> addresses<00:30:26.409> the<00:30:26.769> property 00:30:27.269 --> 00:30:27.279 align:start position:0% this is this addresses the property 00:30:27.279 --> 00:30:28.979 align:start position:0% this is this addresses the property being<00:30:27.519> Ruiz<00:30:27.820> owned<00:30:28.119> in<00:30:28.299> relation<00:30:28.749> to<00:30:28.869> the 00:30:28.979 --> 00:30:28.989 align:start position:0% being Ruiz owned in relation to the 00:30:28.989 --> 00:30:30.570 align:start position:0% being Ruiz owned in relation to the adjacent<00:30:29.230> neighborhood<00:30:29.919> the<00:30:30.070> use<00:30:30.309> is<00:30:30.549> not 00:30:30.570 --> 00:30:30.580 align:start position:0% adjacent neighborhood the use is not 00:30:30.580 --> 00:30:33.149 align:start position:0% adjacent neighborhood the use is not taken<00:30:31.149> into<00:30:31.210> account<00:30:31.389> in<00:30:31.989> this<00:30:32.200> case<00:30:32.559> if<00:30:32.830> okay 00:30:33.149 --> 00:30:33.159 align:start position:0% taken into account in this case if okay 00:30:33.159 --> 00:30:40.529 align:start position:0% taken into account in this case if okay the<00:30:34.590> that<00:30:35.590> could<00:30:35.940> in<00:30:37.019> with<00:30:38.019> this<00:30:38.999> this<00:30:39.999> is<00:30:40.239> the 00:30:40.529 --> 00:30:40.539 align:start position:0% the that could in with this this is the 00:30:40.539 --> 00:30:45.349 align:start position:0% the that could in with this this is the land<00:30:40.809> area<00:30:41.519> being<00:30:42.519> resigned<00:30:43.119> in<00:30:43.559> relation<00:30:44.559> to 00:30:45.349 --> 00:30:45.359 align:start position:0% land area being resigned in relation to 00:30:45.359 --> 00:30:48.989 align:start position:0% land area being resigned in relation to connecting<00:30:46.359> to<00:30:46.600> the<00:30:47.340> streets<00:30:48.340> in<00:30:48.700> the 00:30:48.989 --> 00:30:48.999 align:start position:0% connecting to the streets in the 00:30:48.999 --> 00:30:51.960 align:start position:0% connecting to the streets in the adjacent<00:30:49.239> subdivision<00:30:50.139> so<00:30:50.710> do<00:30:51.009> we<00:30:51.190> if<00:30:51.549> we<00:30:51.730> put 00:30:51.960 --> 00:30:51.970 align:start position:0% adjacent subdivision so do we if we put 00:30:51.970 --> 00:30:53.279 align:start position:0% adjacent subdivision so do we if we put in<00:30:52.119> a<00:30:52.239> shopping<00:30:52.480> center<00:30:52.960> I<00:30:52.989> think<00:30:53.169> this 00:30:53.279 --> 00:30:53.289 align:start position:0% in a shopping center I think this 00:30:53.289 --> 00:30:55.440 align:start position:0% in a shopping center I think this particular<00:30:53.499> concern<00:30:54.279> was<00:30:54.519> that<00:30:54.549> a<00:30:55.090> shopping 00:30:55.440 --> 00:30:55.450 align:start position:0% particular concern was that a shopping 00:30:55.450 --> 00:30:57.810 align:start position:0% particular concern was that a shopping center<00:30:55.809> is<00:30:55.869> going<00:30:56.200> in<00:30:56.470> there's<00:30:57.100> an<00:30:57.279> existing 00:30:57.810 --> 00:30:57.820 align:start position:0% center is going in there's an existing 00:30:57.820 --> 00:30:59.489 align:start position:0% center is going in there's an existing neighborhood<00:30:58.359> and<00:30:58.690> there's<00:30:59.200> going<00:30:59.350> to<00:30:59.440> be 00:30:59.489 --> 00:30:59.499 align:start position:0% neighborhood and there's going to be 00:30:59.499 --> 00:31:02.580 align:start position:0% neighborhood and there's going to be kind<00:31:00.190> of<00:31:00.369> a<00:31:00.580> connection<00:31:01.149> force<00:31:01.840> between<00:31:02.200> the 00:31:02.580 --> 00:31:02.590 align:start position:0% kind of a connection force between the 00:31:02.590 --> 00:31:04.590 align:start position:0% kind of a connection force between the shopping<00:31:03.070> center<00:31:03.460> and<00:31:03.639> the<00:31:03.789> neighborhood<00:31:04.179> and 00:31:04.590 --> 00:31:04.600 align:start position:0% shopping center and the neighborhood and 00:31:04.600 --> 00:31:06.239 align:start position:0% shopping center and the neighborhood and that<00:31:05.109> is<00:31:05.289> the<00:31:05.409> way<00:31:05.559> our<00:31:05.739> connectivity 00:31:06.239 --> 00:31:06.249 align:start position:0% that is the way our connectivity 00:31:06.249 --> 00:31:08.729 align:start position:0% that is the way our connectivity ordinance<00:31:06.820> currently<00:31:07.359> works<00:31:07.989> it's<00:31:08.259> not<00:31:08.440> based 00:31:08.729 --> 00:31:08.739 align:start position:0% ordinance currently works it's not based 00:31:08.739 --> 00:31:10.590 align:start position:0% ordinance currently works it's not based on<00:31:09.009> the<00:31:09.340> it's<00:31:09.639> not<00:31:09.820> based<00:31:10.090> on<00:31:10.239> the<00:31:10.359> adjacent 00:31:10.590 --> 00:31:10.600 align:start position:0% on the it's not based on the adjacent 00:31:10.600 --> 00:31:12.899 align:start position:0% on the it's not based on the adjacent uses<00:31:11.200> it's<00:31:11.440> the<00:31:11.679> presumption<00:31:12.190> that<00:31:12.489> you<00:31:12.639> want 00:31:12.899 --> 00:31:12.909 align:start position:0% uses it's the presumption that you want 00:31:12.909 --> 00:31:15.130 align:start position:0% uses it's the presumption that you want the<00:31:13.419> uses<00:31:13.869> the<00:31:14.200> adjacent<00:31:14.649> uses<00:31:14.950> to 00:31:15.130 --> 00:31:15.140 align:start position:0% the uses the adjacent uses to 00:31:15.140 --> 00:31:19.030 align:start position:0% the uses the adjacent uses to connect<00:31:15.620> and<00:31:15.860> the<00:31:16.930> as<00:31:17.930> is<00:31:18.200> the<00:31:18.410> case<00:31:18.590> now<00:31:18.980> the 00:31:19.030 --> 00:31:19.040 align:start position:0% connect and the as is the case now the 00:31:19.040 --> 00:31:22.870 align:start position:0% connect and the as is the case now the option<00:31:19.820> to<00:31:19.850> go<00:31:20.270> forward<00:31:21.310> after<00:31:22.310> the<00:31:22.430> rezoning 00:31:22.870 --> 00:31:22.880 align:start position:0% option to go forward after the rezoning 00:31:22.880 --> 00:31:24.700 align:start position:0% option to go forward after the rezoning to<00:31:23.240> go<00:31:23.390> forward<00:31:23.930> you<00:31:24.290> know<00:31:24.320> where<00:31:24.620> the 00:31:24.700 --> 00:31:24.710 align:start position:0% to go forward you know where the 00:31:24.710 --> 00:31:28.960 align:start position:0% to go forward you know where the applicant<00:31:25.190> could<00:31:25.430> go<00:31:26.120> to<00:31:27.700> before<00:31:28.700> town 00:31:28.960 --> 00:31:28.970 align:start position:0% applicant could go to before town 00:31:28.970 --> 00:31:32.610 align:start position:0% applicant could go to before town council<00:31:29.750> to<00:31:30.350> see<00:31:30.620> if<00:31:30.920> there<00:31:31.340> are<00:31:31.370> other 00:31:32.610 --> 00:31:32.620 align:start position:0% council to see if there are other 00:31:32.620 --> 00:31:34.930 align:start position:0% council to see if there are other circumstances<00:31:33.620> that<00:31:34.040> town<00:31:34.340> council<00:31:34.820> would 00:31:34.930 --> 00:31:34.940 align:start position:0% circumstances that town council would 00:31:34.940 --> 00:31:36.610 align:start position:0% circumstances that town council would want<00:31:35.120> to<00:31:35.270> waive<00:31:35.450> those<00:31:35.690> requirements<00:31:36.110> through 00:31:36.610 --> 00:31:36.620 align:start position:0% want to waive those requirements through 00:31:36.620 --> 00:31:39.340 align:start position:0% want to waive those requirements through a<00:31:36.920> different<00:31:37.430> process<00:31:37.610> but<00:31:38.390> it<00:31:38.570> wouldn't<00:31:39.200> come 00:31:39.340 --> 00:31:39.350 align:start position:0% a different process but it wouldn't come 00:31:39.350 --> 00:31:43.000 align:start position:0% a different process but it wouldn't come into<00:31:39.530> play<00:31:39.890> at<00:31:40.100> the<00:31:40.250> rezoning<00:31:40.610> process<00:31:42.010> yeah 00:31:43.000 --> 00:31:43.010 align:start position:0% into play at the rezoning process yeah 00:31:43.010 --> 00:31:44.980 align:start position:0% into play at the rezoning process yeah so<00:31:43.280> I<00:31:43.370> can<00:31:43.550> I<00:31:43.730> can<00:31:43.880> understand<00:31:44.390> their<00:31:44.570> concern 00:31:44.980 --> 00:31:44.990 align:start position:0% so I can I can understand their concern 00:31:44.990 --> 00:31:46.840 align:start position:0% so I can I can understand their concern I<00:31:45.020> mean<00:31:45.380> if<00:31:45.500> I<00:31:45.620> could<00:31:45.800> and<00:31:46.100> I<00:31:46.160> it<00:31:46.400> seems<00:31:46.700> like 00:31:46.840 --> 00:31:46.850 align:start position:0% I mean if I could and I it seems like 00:31:46.850 --> 00:31:49.150 align:start position:0% I mean if I could and I it seems like this<00:31:47.060> would<00:31:47.300> be<00:31:47.360> the<00:31:47.630> place<00:31:47.810> to<00:31:48.200> address<00:31:48.770> that 00:31:49.150 --> 00:31:49.160 align:start position:0% this would be the place to address that 00:31:49.160 --> 00:31:52.960 align:start position:0% this would be the place to address that simply<00:31:49.850> and<00:31:49.970> allowing<00:31:50.510> you<00:31:51.410> know<00:31:51.560> that<00:31:52.100> if<00:31:52.550> the 00:31:52.960 --> 00:31:52.970 align:start position:0% simply and allowing you know that if the 00:31:52.970 --> 00:31:55.930 align:start position:0% simply and allowing you know that if the property<00:31:53.600> being<00:31:53.990> rezone<00:31:54.440> diz<00:31:54.770> for<00:31:55.220> commercial 00:31:55.930 --> 00:31:55.940 align:start position:0% property being rezone diz for commercial 00:31:55.940 --> 00:31:57.520 align:start position:0% property being rezone diz for commercial or<00:31:56.180> office<00:31:56.600> you<00:31:56.750> something<00:31:57.170> other<00:31:57.320> than 00:31:57.520 --> 00:31:57.530 align:start position:0% or office you something other than 00:31:57.530 --> 00:32:01.320 align:start position:0% or office you something other than residential<00:31:58.480> then<00:31:59.480> i<00:31:59.900> would<00:32:00.230> think<00:32:00.410> that 00:32:01.320 --> 00:32:01.330 align:start position:0% residential then i would think that 00:32:01.330 --> 00:32:04.180 align:start position:0% residential then i would think that those<00:32:02.330> conditions<00:32:02.870> should<00:32:03.410> be<00:32:03.470> able<00:32:03.740> to<00:32:04.040> be 00:32:04.180 --> 00:32:04.190 align:start position:0% those conditions should be able to be 00:32:04.190 --> 00:32:06.640 align:start position:0% those conditions should be able to be handled<00:32:04.640> during<00:32:04.940> the<00:32:05.210> rezoning<00:32:05.630> because<00:32:06.440> that 00:32:06.640 --> 00:32:06.650 align:start position:0% handled during the rezoning because that 00:32:06.650 --> 00:32:08.560 align:start position:0% handled during the rezoning because that is<00:32:06.830> probably<00:32:07.550> worse<00:32:07.820> than<00:32:07.850> any<00:32:08.300> of<00:32:08.450> these 00:32:08.560 --> 00:32:08.570 align:start position:0% is probably worse than any of these 00:32:08.570 --> 00:32:11.880 align:start position:0% is probably worse than any of these other<00:32:09.220> situations<00:32:10.220> that<00:32:10.430> we've<00:32:10.640> talked<00:32:11.000> about 00:32:11.880 --> 00:32:11.890 align:start position:0% other situations that we've talked about 00:32:11.890 --> 00:32:16.020 align:start position:0% other situations that we've talked about so<00:32:12.890> that<00:32:13.250> i<00:32:13.550> would<00:32:13.970> see<00:32:14.240> is<00:32:14.360> just<00:32:14.390> kind<00:32:14.990> of<00:32:15.080> a 00:32:16.020 --> 00:32:16.030 align:start position:0% so that i would see is just kind of a 00:32:16.030 --> 00:32:18.310 align:start position:0% so that i would see is just kind of a something<00:32:17.030> that<00:32:17.060> i<00:32:17.210> would<00:32:17.330> that<00:32:17.840> that 00:32:18.310 --> 00:32:18.320 align:start position:0% something that i would that that 00:32:18.320 --> 00:32:20.320 align:start position:0% something that i would that that probably<00:32:18.800> should<00:32:19.130> have<00:32:19.190> been<00:32:19.370> added<00:32:19.610> to<00:32:19.940> this 00:32:20.320 --> 00:32:20.330 align:start position:0% probably should have been added to this 00:32:20.330 --> 00:32:23.020 align:start position:0% probably should have been added to this okay<00:32:21.020> well<00:32:21.590> maybe<00:32:21.770> i<00:32:21.920> can<00:32:22.010> offer<00:32:22.370> a<00:32:22.550> little<00:32:22.790> bit 00:32:23.020 --> 00:32:23.030 align:start position:0% okay well maybe i can offer a little bit 00:32:23.030 --> 00:32:24.940 align:start position:0% okay well maybe i can offer a little bit a<00:32:23.390> little<00:32:23.600> bit<00:32:23.810> and<00:32:24.200> i'm<00:32:24.500> glad<00:32:24.650> you<00:32:24.830> brought 00:32:24.940 --> 00:32:24.950 align:start position:0% a little bit and i'm glad you brought 00:32:24.950 --> 00:32:27.820 align:start position:0% a little bit and i'm glad you brought that<00:32:25.010> up<00:32:25.160> tonight<00:32:25.490> um<00:32:25.990> we<00:32:26.990> kind<00:32:27.590> of<00:32:27.680> been 00:32:27.820 --> 00:32:27.830 align:start position:0% that up tonight um we kind of been 00:32:27.830 --> 00:32:31.210 align:start position:0% that up tonight um we kind of been scouring<00:32:28.100> the<00:32:28.910> code<00:32:29.150> about<00:32:30.220> ticket 00:32:31.210 --> 00:32:31.220 align:start position:0% scouring the code about ticket 00:32:31.220 --> 00:32:34.060 align:start position:0% scouring the code about ticket reasonings<00:32:31.790> under<00:32:32.470> zoning<00:32:33.470> districts<00:32:33.920> let 00:32:34.060 --> 00:32:34.070 align:start position:0% reasonings under zoning districts let 00:32:34.070 --> 00:32:36.820 align:start position:0% reasonings under zoning districts let that<00:32:34.250> have<00:32:34.430> better<00:32:35.330> zone<00:32:35.600> MXD<00:32:36.260> that<00:32:36.590> allow<00:32:36.800> a 00:32:36.820 --> 00:32:36.830 align:start position:0% that have better zone MXD that allow a 00:32:36.830 --> 00:32:40.420 align:start position:0% that have better zone MXD that allow a preliminary<00:32:37.370> development<00:32:37.700> plan<00:32:38.560> to<00:32:39.560> be<00:32:39.770> a 00:32:40.420 --> 00:32:40.430 align:start position:0% preliminary development plan to be a 00:32:40.430 --> 00:32:42.130 align:start position:0% preliminary development plan to be a part<00:32:40.940> of<00:32:41.090> that<00:32:41.210> rezoning<00:32:41.630> case<00:32:41.840> so<00:32:41.990> you're 00:32:42.130 --> 00:32:42.140 align:start position:0% part of that rezoning case so you're 00:32:42.140 --> 00:32:44.560 align:start position:0% part of that rezoning case so you're actually<00:32:42.290> seeing<00:32:42.830> everything<00:32:43.790> how<00:32:44.510> the 00:32:44.560 --> 00:32:44.570 align:start position:0% actually seeing everything how the 00:32:44.570 --> 00:32:46.300 align:start position:0% actually seeing everything how the layouts<00:32:45.080> going<00:32:45.380> to<00:32:45.440> be<00:32:45.560> on<00:32:45.680> that<00:32:45.710> plan<00:32:46.070> and 00:32:46.300 --> 00:32:46.310 align:start position:0% layouts going to be on that plan and 00:32:46.310 --> 00:32:48.100 align:start position:0% layouts going to be on that plan and they<00:32:46.400> basically<00:32:46.730> have<00:32:46.910> got<00:32:47.570> to<00:32:47.690> build<00:32:47.870> to<00:32:48.080> that 00:32:48.100 --> 00:32:48.110 align:start position:0% they basically have got to build to that 00:32:48.110 --> 00:32:52.300 align:start position:0% they basically have got to build to that that<00:32:48.650> plan<00:32:49.690> there<00:32:50.690> isn't<00:32:51.020> specific<00:32:51.890> language 00:32:52.300 --> 00:32:52.310 align:start position:0% that plan there isn't specific language 00:32:52.310 --> 00:32:54.550 align:start position:0% that plan there isn't specific language in<00:32:52.520> there<00:32:52.670> that<00:32:52.730> that<00:32:53.270> says<00:32:54.020> you<00:32:54.140> can't<00:32:54.350> look 00:32:54.550 --> 00:32:54.560 align:start position:0% in there that that says you can't look 00:32:54.560 --> 00:32:57.490 align:start position:0% in there that that says you can't look at<00:32:54.740> connectivity<00:32:55.490> I<00:32:55.670> think<00:32:56.510> probably<00:32:56.720> in<00:32:57.350> that 00:32:57.490 --> 00:32:57.500 align:start position:0% at connectivity I think probably in that 00:32:57.500 --> 00:32:59.110 align:start position:0% at connectivity I think probably in that section<00:32:57.770> of<00:32:57.920> the<00:32:58.070> code<00:32:58.250> where<00:32:58.550> talks<00:32:58.790> about 00:32:59.110 --> 00:32:59.120 align:start position:0% section of the code where talks about 00:32:59.120 --> 00:33:01.300 align:start position:0% section of the code where talks about preliminary<00:32:59.960> develop<00:33:00.290> plans<00:33:00.530> we<00:33:01.160> could 00:33:01.300 --> 00:33:01.310 align:start position:0% preliminary develop plans we could 00:33:01.310 --> 00:33:04.240 align:start position:0% preliminary develop plans we could probably<00:33:01.490> strengthen<00:33:02.890> if<00:33:03.890> that's<00:33:04.130> the 00:33:04.240 --> 00:33:04.250 align:start position:0% probably strengthen if that's the 00:33:04.250 --> 00:33:05.890 align:start position:0% probably strengthen if that's the recommendation<00:33:04.520> of<00:33:04.970> this<00:33:05.090> board<00:33:05.390> maybe<00:33:05.600> look 00:33:05.890 --> 00:33:05.900 align:start position:0% recommendation of this board maybe look 00:33:05.900 --> 00:33:08.860 align:start position:0% recommendation of this board maybe look at<00:33:06.080> some<00:33:06.550> opportunities<00:33:07.550> to<00:33:07.640> put<00:33:07.880> some<00:33:08.180> things 00:33:08.860 --> 00:33:08.870 align:start position:0% at some opportunities to put some things 00:33:08.870 --> 00:33:10.420 align:start position:0% at some opportunities to put some things in<00:33:09.140> that<00:33:09.350> part<00:33:09.620> of<00:33:09.710> the<00:33:09.770> code<00:33:10.040> that<00:33:10.280> would 00:33:10.420 --> 00:33:10.430 align:start position:0% in that part of the code that would 00:33:10.430 --> 00:33:12.940 align:start position:0% in that part of the code that would allow<00:33:10.490> connectivity<00:33:11.450> to<00:33:11.600> be<00:33:11.750> to<00:33:12.470> be<00:33:12.500> evaluated 00:33:12.940 --> 00:33:12.950 align:start position:0% allow connectivity to be to be evaluated 00:33:12.950 --> 00:33:16.900 align:start position:0% allow connectivity to be to be evaluated or<00:33:14.200> considered<00:33:15.200> during<00:33:16.010> a<00:33:16.190> preliminary 00:33:16.900 --> 00:33:16.910 align:start position:0% or considered during a preliminary 00:33:16.910 --> 00:33:20.610 align:start position:0% or considered during a preliminary development<00:33:17.240> plan<00:33:17.780> I<00:33:18.770> will<00:33:19.190> tell<00:33:19.400> you<00:33:19.520> that 00:33:20.610 --> 00:33:20.620 align:start position:0% development plan I will tell you that 00:33:20.620 --> 00:33:23.200 align:start position:0% development plan I will tell you that one<00:33:21.620> of<00:33:21.650> the<00:33:21.800> options<00:33:22.010> that<00:33:22.370> counsel<00:33:23.180> was 00:33:23.200 --> 00:33:23.210 align:start position:0% one of the options that counsel was 00:33:23.210 --> 00:33:25.210 align:start position:0% one of the options that counsel was given<00:33:23.990> at<00:33:24.050> their<00:33:24.170> last<00:33:24.290> work<00:33:24.620> session<00:33:25.070> it<00:33:25.130> was 00:33:25.210 --> 00:33:25.220 align:start position:0% given at their last work session it was 00:33:25.220 --> 00:33:27.280 align:start position:0% given at their last work session it was an<00:33:25.340> option<00:33:25.700> where<00:33:25.850> we<00:33:26.240> would<00:33:26.390> you<00:33:27.020> could<00:33:27.170> do<00:33:27.260> a 00:33:27.280 --> 00:33:27.290 align:start position:0% an option where we would you could do a 00:33:27.290 --> 00:33:28.140 align:start position:0% an option where we would you could do a concept<00:33:27.830> plan 00:33:28.140 --> 00:33:28.150 align:start position:0% concept plan 00:33:28.150 --> 00:33:29.280 align:start position:0% concept plan in<00:33:28.210> which<00:33:28.330> which<00:33:28.660> we<00:33:28.810> currently<00:33:28.990> have 00:33:29.280 --> 00:33:29.290 align:start position:0% in which which we currently have 00:33:29.290 --> 00:33:32.640 align:start position:0% in which which we currently have available<00:33:29.500> in<00:33:30.070> the<00:33:30.430> in<00:33:31.270> the<00:33:32.140> code<00:33:32.440> right<00:33:32.590> now 00:33:32.640 --> 00:33:32.650 align:start position:0% available in the in the code right now 00:33:32.650 --> 00:33:34.080 align:start position:0% available in the in the code right now is<00:33:32.950> if<00:33:33.070> you<00:33:33.160> want<00:33:33.310> to<00:33:33.370> do<00:33:33.430> a<00:33:33.460> constant<00:33:33.910> plan 00:33:34.080 --> 00:33:34.090 align:start position:0% is if you want to do a constant plan 00:33:34.090 --> 00:33:36.180 align:start position:0% is if you want to do a constant plan with<00:33:34.270> a<00:33:34.300> rezoning<00:33:34.660> you<00:33:35.320> can<00:33:35.470> do<00:33:35.560> a<00:33:35.590> circulation 00:33:36.180 --> 00:33:36.190 align:start position:0% with a rezoning you can do a circulation 00:33:36.190 --> 00:33:38.400 align:start position:0% with a rezoning you can do a circulation plan<00:33:36.580> and<00:33:36.910> at<00:33:37.300> that<00:33:37.330> time<00:33:37.510> we<00:33:37.900> said<00:33:38.110> that<00:33:38.230> there 00:33:38.400 --> 00:33:38.410 align:start position:0% plan and at that time we said that there 00:33:38.410 --> 00:33:39.750 align:start position:0% plan and at that time we said that there may<00:33:38.590> be<00:33:38.620> an<00:33:38.770> opportunity<00:33:38.980> that<00:33:39.340> we<00:33:39.610> could 00:33:39.750 --> 00:33:39.760 align:start position:0% may be an opportunity that we could 00:33:39.760 --> 00:33:41.190 align:start position:0% may be an opportunity that we could write<00:33:39.970> when<00:33:40.150> we<00:33:40.210> possibly<00:33:40.600> could<00:33:40.780> write<00:33:40.990> in 00:33:41.190 --> 00:33:41.200 align:start position:0% write when we possibly could write in 00:33:41.200 --> 00:33:43.440 align:start position:0% write when we possibly could write in some<00:33:41.830> provisions<00:33:42.310> there<00:33:42.520> were<00:33:42.760> maybe 00:33:43.440 --> 00:33:43.450 align:start position:0% some provisions there were maybe 00:33:43.450 --> 00:33:45.870 align:start position:0% some provisions there were maybe connectivity<00:33:44.140> could<00:33:44.320> be<00:33:44.470> evaluated<00:33:45.280> in<00:33:45.460> that 00:33:45.870 --> 00:33:45.880 align:start position:0% connectivity could be evaluated in that 00:33:45.880 --> 00:33:48.930 align:start position:0% connectivity could be evaluated in that context<00:33:46.510> they<00:33:47.380> didn't<00:33:47.620> have<00:33:47.740> any<00:33:48.040> much 00:33:48.930 --> 00:33:48.940 align:start position:0% context they didn't have any much 00:33:48.940 --> 00:33:53.130 align:start position:0% context they didn't have any much support<00:33:49.360> for<00:33:49.570> that<00:33:49.890> concept<00:33:50.890> plan<00:33:52.140> provision 00:33:53.130 --> 00:33:53.140 align:start position:0% support for that concept plan provision 00:33:53.140 --> 00:33:56.010 align:start position:0% support for that concept plan provision and<00:33:53.470> how<00:33:53.920> connectivity<00:33:54.580> plays<00:33:55.240> into<00:33:55.510> that<00:33:55.690> but 00:33:56.010 --> 00:33:56.020 align:start position:0% and how connectivity plays into that but 00:33:56.020 --> 00:33:58.710 align:start position:0% and how connectivity plays into that but the<00:33:56.740> MX<00:33:57.250> d<00:33:57.400> district<00:33:57.910> and<00:33:58.120> with<00:33:58.360> a<00:33:58.390> polymer 00:33:58.710 --> 00:33:58.720 align:start position:0% the MX d district and with a polymer 00:33:58.720 --> 00:33:59.790 align:start position:0% the MX d district and with a polymer eight<00:33:58.840> of<00:33:58.930> all<00:33:59.020> plan<00:33:59.260> is<00:33:59.380> a<00:33:59.410> little<00:33:59.710> bit 00:33:59.790 --> 00:33:59.800 align:start position:0% eight of all plan is a little bit 00:33:59.800 --> 00:34:01.620 align:start position:0% eight of all plan is a little bit different<00:34:00.220> it<00:34:00.910> actually<00:34:01.060> shows<00:34:01.330> quite 00:34:01.620 --> 00:34:01.630 align:start position:0% different it actually shows quite 00:34:01.630 --> 00:34:03.570 align:start position:0% different it actually shows quite specific<00:34:02.320> about<00:34:02.410> how<00:34:02.950> you<00:34:03.010> going<00:34:03.280> to<00:34:03.310> develop 00:34:03.570 --> 00:34:03.580 align:start position:0% specific about how you going to develop 00:34:03.580 --> 00:34:05.490 align:start position:0% specific about how you going to develop that<00:34:03.700> property<00:34:04.180> so<00:34:04.330> I<00:34:04.360> think<00:34:04.480> there<00:34:04.780> if<00:34:05.200> that's 00:34:05.490 --> 00:34:05.500 align:start position:0% that property so I think there if that's 00:34:05.500 --> 00:34:07.140 align:start position:0% that property so I think there if that's something<00:34:05.710> the<00:34:05.890> board<00:34:06.100> would<00:34:06.280> like<00:34:06.460> staff<00:34:06.970> to 00:34:07.140 --> 00:34:07.150 align:start position:0% something the board would like staff to 00:34:07.150 --> 00:34:09.450 align:start position:0% something the board would like staff to go<00:34:07.180> back<00:34:07.480> before<00:34:07.750> it<00:34:07.990> goes<00:34:08.110> to<00:34:08.290> counsel<00:34:08.800> to 00:34:09.450 --> 00:34:09.460 align:start position:0% go back before it goes to counsel to 00:34:09.460 --> 00:34:11.790 align:start position:0% go back before it goes to counsel to maybe<00:34:09.640> maybe<00:34:10.600> look<00:34:10.929> into<00:34:11.050> that<00:34:11.320> a<00:34:11.380> little<00:34:11.590> bit 00:34:11.790 --> 00:34:11.800 align:start position:0% maybe maybe look into that a little bit 00:34:11.800 --> 00:34:14.880 align:start position:0% maybe maybe look into that a little bit more<00:34:12.070> we<00:34:12.700> certainly<00:34:13.000> could<00:34:13.210> do<00:34:13.360> that<00:34:13.540> I<00:34:13.890> think 00:34:14.880 --> 00:34:14.890 align:start position:0% more we certainly could do that I think 00:34:14.890 --> 00:34:16.800 align:start position:0% more we certainly could do that I think that<00:34:15.130> would<00:34:15.310> be<00:34:15.490> a<00:34:15.520> good<00:34:15.669> idea<00:34:15.730> because<00:34:16.210> as<00:34:16.630> I 00:34:16.800 --> 00:34:16.810 align:start position:0% that would be a good idea because as I 00:34:16.810 --> 00:34:18.180 align:start position:0% that would be a good idea because as I was<00:34:16.960> reading<00:34:17.169> this<00:34:17.409> whole<00:34:17.649> thing<00:34:17.890> i<00:34:18.040> was 00:34:18.180 --> 00:34:18.190 align:start position:0% was reading this whole thing i was 00:34:18.190 --> 00:34:19.620 align:start position:0% was reading this whole thing i was thinking<00:34:18.220> neighborhood<00:34:19.030> in<00:34:19.149> neighborhood 00:34:19.620 --> 00:34:19.630 align:start position:0% thinking neighborhood in neighborhood 00:34:19.630 --> 00:34:25.860 align:start position:0% thinking neighborhood in neighborhood and<00:34:21.840> you<00:34:22.840> know<00:34:23.020> i<00:34:23.980> don't<00:34:24.399> i'm<00:34:25.000> not<00:34:25.060> up<00:34:25.480> on<00:34:25.690> the 00:34:25.860 --> 00:34:25.870 align:start position:0% and you know i don't i'm not up on the 00:34:25.870 --> 00:34:29.159 align:start position:0% and you know i don't i'm not up on the connectivity<00:34:26.440> requirements<00:34:27.399> for<00:34:27.700> em<00:34:28.030> XD<00:34:28.630> or 00:34:29.159 --> 00:34:29.169 align:start position:0% connectivity requirements for em XD or 00:34:29.169 --> 00:34:31.139 align:start position:0% connectivity requirements for em XD or plain<00:34:29.679> commercial<00:34:30.130> or<00:34:30.310> office<00:34:30.730> or<00:34:30.820> anything 00:34:31.139 --> 00:34:31.149 align:start position:0% plain commercial or office or anything 00:34:31.149 --> 00:34:33.000 align:start position:0% plain commercial or office or anything else<00:34:31.300> but<00:34:31.480> it<00:34:31.600> seems<00:34:31.840> to<00:34:31.929> me<00:34:32.110> like<00:34:32.140> that<00:34:32.649> should 00:34:33.000 --> 00:34:33.010 align:start position:0% else but it seems to me like that should 00:34:33.010 --> 00:34:35.430 align:start position:0% else but it seems to me like that should be<00:34:33.040> a<00:34:33.600> factor<00:34:34.600> in<00:34:34.690> this<00:34:34.810> because<00:34:35.080> it's 00:34:35.430 --> 00:34:35.440 align:start position:0% be a factor in this because it's 00:34:35.440 --> 00:34:37.919 align:start position:0% be a factor in this because it's definitely<00:34:35.620> something<00:34:36.250> that<00:34:36.399> should<00:34:36.790> be<00:34:37.000> it 00:34:37.919 --> 00:34:37.929 align:start position:0% definitely something that should be it 00:34:37.929 --> 00:34:39.630 align:start position:0% definitely something that should be it would<00:34:38.110> give<00:34:38.260> people<00:34:38.590> such<00:34:38.830> peace<00:34:39.100> of<00:34:39.280> mind<00:34:39.490> if 00:34:39.630 --> 00:34:39.640 align:start position:0% would give people such peace of mind if 00:34:39.640 --> 00:34:42.030 align:start position:0% would give people such peace of mind if we<00:34:39.760> could<00:34:39.909> address<00:34:40.210> it<00:34:40.330> at<00:34:40.630> rezoning<00:34:41.110> right 00:34:42.030 --> 00:34:42.040 align:start position:0% we could address it at rezoning right 00:34:42.040 --> 00:34:45.560 align:start position:0% we could address it at rezoning right and<00:34:42.220> it<00:34:42.310> could<00:34:42.730> very<00:34:42.940> well<00:34:43.000> be<00:34:43.270> that<00:34:43.300> that<00:34:44.550> a 00:34:45.560 --> 00:34:45.570 align:start position:0% and it could very well be that that a 00:34:45.570 --> 00:34:47.580 align:start position:0% and it could very well be that that a neighborhood<00:34:46.570> adjacent<00:34:46.690> to<00:34:47.200> a<00:34:47.230> commercial 00:34:47.580 --> 00:34:47.590 align:start position:0% neighborhood adjacent to a commercial 00:34:47.590 --> 00:34:50.690 align:start position:0% neighborhood adjacent to a commercial area<00:34:48.040> could<00:34:48.520> be<00:34:48.580> quite<00:34:48.880> compatible<00:34:49.530> having<00:34:50.530> a 00:34:50.690 --> 00:34:50.700 align:start position:0% area could be quite compatible having a 00:34:50.700 --> 00:34:54.180 align:start position:0% area could be quite compatible having a secondary<00:34:51.700> access<00:34:52.240> into<00:34:53.080> a<00:34:53.110> shopping<00:34:53.409> area<00:34:53.710> so 00:34:54.180 --> 00:34:54.190 align:start position:0% secondary access into a shopping area so 00:34:54.190 --> 00:34:56.010 align:start position:0% secondary access into a shopping area so it's<00:34:54.340> convenient<00:34:54.880> so<00:34:55.450> that<00:34:55.659> people<00:34:55.990> don't 00:34:56.010 --> 00:34:56.020 align:start position:0% it's convenient so that people don't 00:34:56.020 --> 00:34:57.750 align:start position:0% it's convenient so that people don't have<00:34:56.260> to<00:34:56.320> get<00:34:56.530> out<00:34:56.679> on<00:34:56.830> a<00:34:56.860> thoroughfare<00:34:57.250> just 00:34:57.750 --> 00:34:57.760 align:start position:0% have to get out on a thoroughfare just 00:34:57.760 --> 00:34:59.910 align:start position:0% have to get out on a thoroughfare just to<00:34:58.090> do<00:34:58.240> that<00:34:58.450> but<00:34:58.990> i<00:34:59.020> think<00:34:59.080> there's<00:34:59.530> there 00:34:59.910 --> 00:34:59.920 align:start position:0% to do that but i think there's there 00:34:59.920 --> 00:35:02.400 align:start position:0% to do that but i think there's there there<00:35:00.430> are<00:35:00.610> ways<00:35:00.880> to<00:35:00.910> achieve<00:35:01.410> connectivity 00:35:02.400 --> 00:35:02.410 align:start position:0% there are ways to achieve connectivity 00:35:02.410 --> 00:35:06.210 align:start position:0% there are ways to achieve connectivity and<00:35:03.180> and<00:35:04.180> and<00:35:04.780> still<00:35:05.140> you<00:35:05.560> know<00:35:05.710> and<00:35:05.980> still 00:35:06.210 --> 00:35:06.220 align:start position:0% and and and still you know and still 00:35:06.220 --> 00:35:08.100 align:start position:0% and and and still you know and still keep<00:35:06.580> it<00:35:06.820> a<00:35:06.940> balance<00:35:07.390> such<00:35:07.600> that<00:35:07.810> we're<00:35:07.960> not 00:35:08.100 --> 00:35:08.110 align:start position:0% keep it a balance such that we're not 00:35:08.110 --> 00:35:10.950 align:start position:0% keep it a balance such that we're not having<00:35:08.500> shopping<00:35:09.310> center<00:35:09.610> traffic<00:35:10.060> going 00:35:10.950 --> 00:35:10.960 align:start position:0% having shopping center traffic going 00:35:10.960 --> 00:35:12.240 align:start position:0% having shopping center traffic going through<00:35:11.170> a<00:35:11.230> neighborhood<00:35:11.710> as<00:35:11.860> its<00:35:12.040> primary 00:35:12.240 --> 00:35:12.250 align:start position:0% through a neighborhood as its primary 00:35:12.250 --> 00:35:14.340 align:start position:0% through a neighborhood as its primary entrance<00:35:12.880> you<00:35:13.270> know<00:35:13.390> there's<00:35:14.080> a<00:35:14.170> lot<00:35:14.320> of 00:35:14.340 --> 00:35:14.350 align:start position:0% entrance you know there's a lot of 00:35:14.350 --> 00:35:16.890 align:start position:0% entrance you know there's a lot of creative<00:35:14.890> ways<00:35:14.980> from<00:35:15.490> a<00:35:15.610> land<00:35:15.850> land<00:35:16.630> planning 00:35:16.890 --> 00:35:16.900 align:start position:0% creative ways from a land land planning 00:35:16.900 --> 00:35:19.320 align:start position:0% creative ways from a land land planning perspective<00:35:17.590> traffic<00:35:18.370> calming<00:35:18.700> perspective 00:35:19.320 --> 00:35:19.330 align:start position:0% perspective traffic calming perspective 00:35:19.330 --> 00:35:20.660 align:start position:0% perspective traffic calming perspective that<00:35:19.510> they<00:35:19.630> could<00:35:19.810> integrate<00:35:19.990> into<00:35:20.470> their 00:35:20.660 --> 00:35:20.670 align:start position:0% that they could integrate into their 00:35:20.670 --> 00:35:23.010 align:start position:0% that they could integrate into their shopping<00:35:21.670> center<00:35:22.030> plan<00:35:22.270> to<00:35:22.480> make<00:35:22.630> that<00:35:22.750> happen 00:35:23.010 --> 00:35:23.020 align:start position:0% shopping center plan to make that happen 00:35:23.020 --> 00:35:25.410 align:start position:0% shopping center plan to make that happen so<00:35:23.440> it<00:35:23.560> just<00:35:23.740> depends<00:35:24.040> on<00:35:24.160> how<00:35:24.310> how<00:35:24.850> creative 00:35:25.410 --> 00:35:25.420 align:start position:0% so it just depends on how how creative 00:35:25.420 --> 00:35:27.630 align:start position:0% so it just depends on how how creative you<00:35:25.450> want<00:35:25.810> to<00:35:25.930> be<00:35:26.050> that<00:35:26.200> to<00:35:26.410> discourage<00:35:27.010> cut 00:35:27.630 --> 00:35:27.640 align:start position:0% you want to be that to discourage cut 00:35:27.640 --> 00:35:29.910 align:start position:0% you want to be that to discourage cut through<00:35:27.820> traffic<00:35:28.000> that<00:35:28.450> shouldn't<00:35:28.810> be<00:35:28.960> going 00:35:29.910 --> 00:35:29.920 align:start position:0% through traffic that shouldn't be going 00:35:29.920 --> 00:35:31.650 align:start position:0% through traffic that shouldn't be going from<00:35:30.640> the<00:35:30.790> shopping<00:35:31.150> center<00:35:31.420> through<00:35:31.600> a 00:35:31.650 --> 00:35:31.660 align:start position:0% from the shopping center through a 00:35:31.660 --> 00:35:33.030 align:start position:0% from the shopping center through a neighborhood<00:35:32.110> so<00:35:32.410> i<00:35:32.440> think<00:35:32.590> that's<00:35:32.830> really 00:35:33.030 --> 00:35:33.040 align:start position:0% neighborhood so i think that's really 00:35:33.040 --> 00:35:34.710 align:start position:0% neighborhood so i think that's really kind<00:35:33.910> of<00:35:34.000> up<00:35:34.090> to<00:35:34.120> the<00:35:34.210> development<00:35:34.690> community 00:35:34.710 --> 00:35:34.720 align:start position:0% kind of up to the development community 00:35:34.720 --> 00:35:36.480 align:start position:0% kind of up to the development community to<00:35:35.050> kind<00:35:35.230> of<00:35:35.350> kind<00:35:35.620> of<00:35:35.740> work<00:35:35.890> on<00:35:36.070> it<00:35:36.220> but<00:35:36.370> it's 00:35:36.480 --> 00:35:36.490 align:start position:0% to kind of kind of work on it but it's 00:35:36.490 --> 00:35:39.270 align:start position:0% to kind of kind of work on it but it's certainly<00:35:36.660> there<00:35:37.660> is<00:35:37.840> there<00:35:38.170> is<00:35:38.280> opportunity 00:35:39.270 --> 00:35:39.280 align:start position:0% certainly there is there is opportunity 00:35:39.280 --> 00:35:41.000 align:start position:0% certainly there is there is opportunity maybe<00:35:39.550> during<00:35:39.790> a<00:35:39.910> rezoning<00:35:40.270> is<00:35:40.660> about 00:35:41.000 --> 00:35:41.010 align:start position:0% maybe during a rezoning is about 00:35:41.010 --> 00:35:43.100 align:start position:0% maybe during a rezoning is about you<00:35:41.070> waiting<00:35:41.600> material<00:35:42.600> particularly<00:35:42.870> during 00:35:43.100 --> 00:35:43.110 align:start position:0% you waiting material particularly during 00:35:43.110 --> 00:35:44.900 align:start position:0% you waiting material particularly during a<00:35:43.230> polarity<00:35:43.890> develop<00:35:44.220> plan<00:35:44.400> to<00:35:44.520> look<00:35:44.670> at<00:35:44.790> it 00:35:44.900 --> 00:35:44.910 align:start position:0% a polarity develop plan to look at it 00:35:44.910 --> 00:35:49.610 align:start position:0% a polarity develop plan to look at it that<00:35:45.600> way<00:35:47.300> um<00:35:48.300> I<00:35:48.450> think<00:35:48.660> the<00:35:49.050> key<00:35:49.290> word<00:35:49.320> in 00:35:49.610 --> 00:35:49.620 align:start position:0% that way um I think the key word in 00:35:49.620 --> 00:35:51.560 align:start position:0% that way um I think the key word in there<00:35:49.740> was<00:35:49.920> cut<00:35:50.160> through<00:35:50.370> I<00:35:50.580> like<00:35:51.330> the<00:35:51.480> idea 00:35:51.560 --> 00:35:51.570 align:start position:0% there was cut through I like the idea 00:35:51.570 --> 00:35:53.630 align:start position:0% there was cut through I like the idea that<00:35:51.840> some<00:35:52.230> people<00:35:52.470> might<00:35:52.650> want<00:35:52.950> to<00:35:53.250> be<00:35:53.580> able 00:35:53.630 --> 00:35:53.640 align:start position:0% that some people might want to be able 00:35:53.640 --> 00:35:56.810 align:start position:0% that some people might want to be able to<00:35:53.940> get<00:35:54.120> there<00:35:54.530> and<00:35:55.530> even<00:35:56.100> if<00:35:56.190> it's<00:35:56.310> like<00:35:56.400> what 00:35:56.810 --> 00:35:56.820 align:start position:0% to get there and even if it's like what 00:35:56.820 --> 00:35:59.060 align:start position:0% to get there and even if it's like what school<00:35:57.450> is<00:35:57.660> that<00:35:57.750> what<00:35:58.080> kind<00:35:58.560> of<00:35:58.650> zona<00:35:58.890> does 00:35:59.060 --> 00:35:59.070 align:start position:0% school is that what kind of zona does 00:35:59.070 --> 00:36:01.760 align:start position:0% school is that what kind of zona does the<00:35:59.160> school<00:35:59.280> go<00:35:59.490> into<00:35:59.900> I'm<00:36:00.900> sorry<00:36:01.350> what<00:36:01.500> kind 00:36:01.760 --> 00:36:01.770 align:start position:0% the school go into I'm sorry what kind 00:36:01.770 --> 00:36:03.830 align:start position:0% the school go into I'm sorry what kind of<00:36:01.860> Zoning<00:36:02.190> what<00:36:02.280> a<00:36:02.310> school<00:36:02.610> go<00:36:02.730> into<00:36:03.030> what<00:36:03.810> a 00:36:03.830 --> 00:36:03.840 align:start position:0% of Zoning what a school go into what a 00:36:03.840 --> 00:36:06.980 align:start position:0% of Zoning what a school go into what a school<00:36:04.140> go<00:36:04.320> into<00:36:04.680> going<00:36:05.220> to<00:36:05.310> a<00:36:05.930> number<00:36:06.930> of 00:36:06.980 --> 00:36:06.990 align:start position:0% school go into going to a number of 00:36:06.990 --> 00:36:08.540 align:start position:0% school go into going to a number of different<00:36:07.140> zone<00:36:07.500> yes<00:36:07.740> okay<00:36:08.100> because<00:36:08.370> some 00:36:08.540 --> 00:36:08.550 align:start position:0% different zone yes okay because some 00:36:08.550 --> 00:36:10.550 align:start position:0% different zone yes okay because some people<00:36:08.940> would<00:36:09.120> want<00:36:09.450> a<00:36:09.630> connectivity<00:36:10.200> or<00:36:10.410> a 00:36:10.550 --> 00:36:10.560 align:start position:0% people would want a connectivity or a 00:36:10.560 --> 00:36:12.440 align:start position:0% people would want a connectivity or a walking<00:36:10.920> path<00:36:11.070> so<00:36:11.490> I<00:36:11.790> don't<00:36:11.880> know<00:36:12.090> if<00:36:12.330> when 00:36:12.440 --> 00:36:12.450 align:start position:0% walking path so I don't know if when 00:36:12.450 --> 00:36:13.430 align:start position:0% walking path so I don't know if when you're<00:36:12.570> doing<00:36:12.780> all<00:36:12.900> those<00:36:13.020> things<00:36:13.080> if<00:36:13.410> you 00:36:13.430 --> 00:36:13.440 align:start position:0% you're doing all those things if you 00:36:13.440 --> 00:36:16.130 align:start position:0% you're doing all those things if you would<00:36:13.590> keep<00:36:13.680> that<00:36:13.860> in<00:36:13.980> mind<00:36:14.100> too<00:36:14.840> yeah<00:36:15.840> I'm 00:36:16.130 --> 00:36:16.140 align:start position:0% would keep that in mind too yeah I'm 00:36:16.140 --> 00:36:17.870 align:start position:0% would keep that in mind too yeah I'm just<00:36:16.380> saying<00:36:16.620> it<00:36:16.800> should<00:36:17.010> be<00:36:17.040> addressed<00:36:17.640> here 00:36:17.870 --> 00:36:17.880 align:start position:0% just saying it should be addressed here 00:36:17.880 --> 00:36:19.730 align:start position:0% just saying it should be addressed here I<00:36:18.060> think<00:36:18.510> the<00:36:18.570> key<00:36:18.780> word<00:36:18.810> was<00:36:18.960> cut<00:36:19.290> from<00:36:19.440> you<00:36:19.620> we 00:36:19.730 --> 00:36:19.740 align:start position:0% I think the key word was cut from you we 00:36:19.740 --> 00:36:21.260 align:start position:0% I think the key word was cut from you we don't<00:36:19.860> we<00:36:20.220> see<00:36:20.400> i<00:36:20.430> agree<00:36:20.910> with<00:36:20.940> you<00:36:21.060> i<00:36:21.120> thought 00:36:21.260 --> 00:36:21.270 align:start position:0% don't we see i agree with you i thought 00:36:21.270 --> 00:36:22.580 align:start position:0% don't we see i agree with you i thought it<00:36:21.360> was<00:36:21.420> residential<00:36:21.930> or<00:36:22.020> residential<00:36:22.380> we 00:36:22.580 --> 00:36:22.590 align:start position:0% it was residential or residential we 00:36:22.590 --> 00:36:24.500 align:start position:0% it was residential or residential we don't<00:36:22.710> somebody<00:36:22.950> have<00:36:23.220> cut<00:36:23.850> the<00:36:23.940> guy<00:36:24.150> so<00:36:24.450> you 00:36:24.500 --> 00:36:24.510 align:start position:0% don't somebody have cut the guy so you 00:36:24.510 --> 00:36:25.670 align:start position:0% don't somebody have cut the guy so you brought<00:36:24.780> that<00:36:24.840> thank<00:36:25.200> you<00:36:25.320> for<00:36:25.410> bringing<00:36:25.590> that 00:36:25.670 --> 00:36:25.680 align:start position:0% brought that thank you for bringing that 00:36:25.680 --> 00:36:29.390 align:start position:0% brought that thank you for bringing that out<00:36:25.770> room<00:36:26.040> and<00:36:27.030> I<00:36:27.840> could<00:36:27.990> we<00:36:28.620> can<00:36:28.890> take<00:36:29.100> a<00:36:29.130> look 00:36:29.390 --> 00:36:29.400 align:start position:0% out room and I could we can take a look 00:36:29.400 --> 00:36:31.640 align:start position:0% out room and I could we can take a look at<00:36:29.550> the<00:36:29.640> ordinate<00:36:30.030> stoop<00:36:30.330> with<00:36:30.810> the<00:36:31.020> specific 00:36:31.640 --> 00:36:31.650 align:start position:0% at the ordinate stoop with the specific 00:36:31.650 --> 00:36:33.680 align:start position:0% at the ordinate stoop with the specific question<00:36:32.040> related<00:36:32.400> to<00:36:32.430> the<00:36:32.610> M<00:36:32.730> XD<00:36:33.120> district 00:36:33.680 --> 00:36:33.690 align:start position:0% question related to the M XD district 00:36:33.690 --> 00:36:38.330 align:start position:0% question related to the M XD district and<00:36:33.900> see<00:36:34.880> you<00:36:35.880> know<00:36:36.380> see<00:36:37.380> how<00:36:37.500> far<00:36:37.770> our<00:36:37.980> current 00:36:38.330 --> 00:36:38.340 align:start position:0% and see you know see how far our current 00:36:38.340 --> 00:36:39.620 align:start position:0% and see you know see how far our current ordinance<00:36:38.580> goes<00:36:38.910> there<00:36:39.120> may<00:36:39.270> be<00:36:39.300> some 00:36:39.620 --> 00:36:39.630 align:start position:0% ordinance goes there may be some 00:36:39.630 --> 00:36:42.080 align:start position:0% ordinance goes there may be some flexibility<00:36:40.320> that<00:36:40.670> flexibility<00:36:41.670> that<00:36:41.880> we 00:36:42.080 --> 00:36:42.090 align:start position:0% flexibility that flexibility that we 00:36:42.090 --> 00:36:45.200 align:start position:0% flexibility that flexibility that we have<00:36:42.330> within<00:36:42.780> that<00:36:43.290> particular<00:36:44.210> district 00:36:45.200 --> 00:36:45.210 align:start position:0% have within that particular district 00:36:45.210 --> 00:36:46.820 align:start position:0% have within that particular district because<00:36:45.540> since<00:36:46.050> we<00:36:46.170> do<00:36:46.320> have<00:36:46.350> the<00:36:46.620> preliminary 00:36:46.820 --> 00:36:46.830 align:start position:0% because since we do have the preliminary 00:36:46.830 --> 00:36:48.530 align:start position:0% because since we do have the preliminary development<00:36:47.280> plan<00:36:47.790> so<00:36:47.940> we<00:36:48.060> can<00:36:48.210> take<00:36:48.390> a<00:36:48.420> look 00:36:48.530 --> 00:36:48.540 align:start position:0% development plan so we can take a look 00:36:48.540 --> 00:36:51.110 align:start position:0% development plan so we can take a look at<00:36:48.780> that<00:36:49.370> and<00:36:50.370> see<00:36:50.580> if<00:36:50.610> there's<00:36:50.880> any 00:36:51.110 --> 00:36:51.120 align:start position:0% at that and see if there's any 00:36:51.120 --> 00:36:54.380 align:start position:0% at that and see if there's any additional<00:36:51.960> applicability<00:36:52.620> that<00:36:53.210> comes<00:36:54.210> into 00:36:54.380 --> 00:36:54.390 align:start position:0% additional applicability that comes into 00:36:54.390 --> 00:37:04.040 align:start position:0% additional applicability that comes into play<00:36:54.630> there<00:37:01.910> frequently<00:37:02.910> we<00:37:03.330> run<00:37:03.600> into<00:37:03.780> the 00:37:04.040 --> 00:37:04.050 align:start position:0% play there frequently we run into the 00:37:04.050 --> 00:37:08.290 align:start position:0% play there frequently we run into the issue<00:37:04.080> of<00:37:04.620> top<00:37:05.010> ography<00:37:05.970> or<00:37:06.810> stream<00:37:07.470> buffers 00:37:08.290 --> 00:37:08.300 align:start position:0% issue of top ography or stream buffers 00:37:08.300 --> 00:37:12.350 align:start position:0% issue of top ography or stream buffers when<00:37:09.300> we're<00:37:09.480> looking<00:37:09.600> at<00:37:09.900> a<00:37:09.930> rezoning<00:37:11.360> where 00:37:12.350 --> 00:37:12.360 align:start position:0% when we're looking at a rezoning where 00:37:12.360 --> 00:37:15.920 align:start position:0% when we're looking at a rezoning where would<00:37:12.540> that<00:37:12.600> come<00:37:12.780> into<00:37:13.230> play<00:37:14.630> that<00:37:15.630> comes 00:37:15.920 --> 00:37:15.930 align:start position:0% would that come into play that comes 00:37:15.930 --> 00:37:19.550 align:start position:0% would that come into play that comes into<00:37:16.200> play<00:37:16.740> in<00:37:17.190> the<00:37:17.700> end<00:37:18.120> that<00:37:18.690> that's<00:37:18.900> the<00:37:19.200> air 00:37:19.550 --> 00:37:19.560 align:start position:0% into play in the end that that's the air 00:37:19.560 --> 00:37:23.000 align:start position:0% into play in the end that that's the air one<00:37:20.160> area<00:37:20.520> where<00:37:20.790> the<00:37:20.970> planning<00:37:21.420> director<00:37:22.010> can 00:37:23.000 --> 00:37:23.010 align:start position:0% one area where the planning director can 00:37:23.010 --> 00:37:26.690 align:start position:0% one area where the planning director can have<00:37:23.280> some<00:37:23.640> discretion<00:37:24.710> in<00:37:25.710> looking<00:37:26.340> at<00:37:26.520> the 00:37:26.690 --> 00:37:26.700 align:start position:0% have some discretion in looking at the 00:37:26.700 --> 00:37:30.950 align:start position:0% have some discretion in looking at the specific<00:37:27.590> topography<00:37:28.590> and<00:37:29.750> potentially<00:37:30.750> wave 00:37:30.950 --> 00:37:30.960 align:start position:0% specific topography and potentially wave 00:37:30.960 --> 00:37:34.040 align:start position:0% specific topography and potentially wave a<00:37:30.990> connection<00:37:31.740> for<00:37:32.100> that<00:37:32.280> reason<00:37:32.630> if<00:37:33.630> it's<00:37:33.870> not 00:37:34.040 --> 00:37:34.050 align:start position:0% a connection for that reason if it's not 00:37:34.050 --> 00:37:36.370 align:start position:0% a connection for that reason if it's not feasible<00:37:34.290> due<00:37:34.800> to<00:37:34.950> a<00:37:35.240> typographic 00:37:36.370 --> 00:37:36.380 align:start position:0% feasible due to a typographic 00:37:36.380 --> 00:37:39.140 align:start position:0% feasible due to a typographic differences<00:37:37.380> in<00:37:37.590> streams<00:37:38.010> and<00:37:38.250> stream 00:37:39.140 --> 00:37:39.150 align:start position:0% differences in streams and stream 00:37:39.150 --> 00:37:41.780 align:start position:0% differences in streams and stream crossings<00:37:39.750> and<00:37:40.160> floodplain<00:37:41.160> areas<00:37:41.520> can 00:37:41.780 --> 00:37:41.790 align:start position:0% crossings and floodplain areas can 00:37:41.790 --> 00:37:47.270 align:start position:0% crossings and floodplain areas can certainly<00:37:42.150> play<00:37:43.140> into<00:37:43.500> that<00:37:45.740> so<00:37:46.740> it's<00:37:46.980> that 00:37:47.270 --> 00:37:47.280 align:start position:0% certainly play into that so it's that 00:37:47.280 --> 00:37:48.950 align:start position:0% certainly play into that so it's that one<00:37:47.520> quick<00:37:47.760> question<00:37:48.060> mayor<00:37:48.510> one<00:37:48.720> point 00:37:48.950 --> 00:37:48.960 align:start position:0% one quick question mayor one point 00:37:48.960 --> 00:37:51.250 align:start position:0% one quick question mayor one point clarifications<00:37:49.560> on<00:37:49.680> that<00:37:49.860> last<00:37:50.040> point 00:37:51.250 --> 00:37:51.260 align:start position:0% clarifications on that last point 00:37:51.260 --> 00:37:52.840 align:start position:0% clarifications on that last point I<00:37:51.350> know<00:37:52.040> it's<00:37:52.220> none<00:37:52.310> of<00:37:52.370> the<00:37:52.520> current 00:37:52.840 --> 00:37:52.850 align:start position:0% I know it's none of the current 00:37:52.850 --> 00:37:55.090 align:start position:0% I know it's none of the current requirements<00:37:53.540> from<00:37:53.990> connectivity<00:37:54.710> so<00:37:54.950> that 00:37:55.090 --> 00:37:55.100 align:start position:0% requirements from connectivity so that 00:37:55.100 --> 00:37:56.800 align:start position:0% requirements from connectivity so that would<00:37:55.250> still<00:37:55.520> remain<00:37:55.760> that<00:37:56.420> the<00:37:56.540> planning 00:37:56.800 --> 00:37:56.810 align:start position:0% would still remain that the planning 00:37:56.810 --> 00:37:58.330 align:start position:0% would still remain that the planning director<00:37:57.110> would<00:37:57.230> still<00:37:57.440> I<00:37:57.470> mean<00:37:57.800> I<00:37:57.830> always 00:37:58.330 --> 00:37:58.340 align:start position:0% director would still I mean I always 00:37:58.340 --> 00:38:00.000 align:start position:0% director would still I mean I always think<00:37:58.460> about<00:37:58.640> as<00:37:58.880> we<00:37:59.030> were<00:37:59.120> looking<00:37:59.660> at<00:37:59.750> these 00:38:00.000 --> 00:38:00.010 align:start position:0% think about as we were looking at these 00:38:00.010 --> 00:38:03.400 align:start position:0% think about as we were looking at these ldos<00:38:01.010> as<00:38:01.280> I<00:38:01.460> true<00:38:01.700> word<00:38:01.850> it's<00:38:02.780> difficult<00:38:03.260> to 00:38:03.400 --> 00:38:03.410 align:start position:0% ldos as I true word it's difficult to 00:38:03.410 --> 00:38:04.900 align:start position:0% ldos as I true word it's difficult to cover<00:38:03.620> a<00:38:03.740> hundred<00:38:04.010> percent<00:38:04.100> so<00:38:04.580> you<00:38:04.640> have 00:38:04.900 --> 00:38:04.910 align:start position:0% cover a hundred percent so you have 00:38:04.910 --> 00:38:07.090 align:start position:0% cover a hundred percent so you have these<00:38:05.060> you<00:38:05.480> know<00:38:05.600> those<00:38:06.080> one<00:38:06.350> and<00:38:06.500> two<00:38:06.650> percent 00:38:07.090 --> 00:38:07.100 align:start position:0% these you know those one and two percent 00:38:07.100 --> 00:38:09.310 align:start position:0% these you know those one and two percent and<00:38:07.340> just<00:38:07.490> kind<00:38:07.670> of<00:38:07.700> that<00:38:07.880> process<00:38:08.150> so<00:38:09.020> in 00:38:09.310 --> 00:38:09.320 align:start position:0% and just kind of that process so in 00:38:09.320 --> 00:38:10.930 align:start position:0% and just kind of that process so in those<00:38:09.440> cases<00:38:09.500> where<00:38:10.100> there's<00:38:10.280> topography<00:38:10.910> or 00:38:10.930 --> 00:38:10.940 align:start position:0% those cases where there's topography or 00:38:10.940 --> 00:38:12.520 align:start position:0% those cases where there's topography or some<00:38:11.240> other<00:38:11.360> physical<00:38:11.600> constraint<00:38:12.350> whether 00:38:12.520 --> 00:38:12.530 align:start position:0% some other physical constraint whether 00:38:12.530 --> 00:38:15.460 align:start position:0% some other physical constraint whether it<00:38:12.620> be<00:38:12.770> a<00:38:13.300> wetland<00:38:14.300> or<00:38:14.570> something<00:38:15.080> else<00:38:15.230> that's 00:38:15.460 --> 00:38:15.470 align:start position:0% it be a wetland or something else that's 00:38:15.470 --> 00:38:17.020 align:start position:0% it be a wetland or something else that's in<00:38:15.770> some<00:38:16.070> of<00:38:16.190> the<00:38:16.280> natural<00:38:16.460> item<00:38:16.880> that's 00:38:17.020 --> 00:38:17.030 align:start position:0% in some of the natural item that's 00:38:17.030 --> 00:38:19.420 align:start position:0% in some of the natural item that's developed<00:38:17.570> there<00:38:17.750> that<00:38:18.100> that<00:38:19.100> could<00:38:19.310> get 00:38:19.420 --> 00:38:19.430 align:start position:0% developed there that that could get 00:38:19.430 --> 00:38:22.810 align:start position:0% developed there that that could get resolved<00:38:19.930> that<00:38:20.930> can<00:38:21.140> be<00:38:21.290> resolved<00:38:21.620> earlier<00:38:22.190> we 00:38:22.810 --> 00:38:22.820 align:start position:0% resolved that can be resolved earlier we 00:38:22.820 --> 00:38:25.360 align:start position:0% resolved that can be resolved earlier we have<00:38:23.060> had<00:38:23.330> cases<00:38:24.110> before<00:38:24.500> I<00:38:24.710> believe<00:38:25.070> where 00:38:25.360 --> 00:38:25.370 align:start position:0% have had cases before I believe where 00:38:25.370 --> 00:38:28.060 align:start position:0% have had cases before I believe where we've<00:38:26.210> asked<00:38:26.750> the<00:38:26.870> planning<00:38:27.380> director<00:38:27.890> to 00:38:28.060 --> 00:38:28.070 align:start position:0% we've asked the planning director to 00:38:28.070 --> 00:38:32.010 align:start position:0% we've asked the planning director to make<00:38:28.100> a<00:38:28.310> determination<00:38:29.180> on<00:38:30.170> the<00:38:30.730> on<00:38:31.730> a 00:38:32.010 --> 00:38:32.020 align:start position:0% make a determination on the on a 00:38:32.020 --> 00:38:35.320 align:start position:0% make a determination on the on a connection<00:38:33.020> issue<00:38:33.730> rather<00:38:34.730> than<00:38:34.940> waiting 00:38:35.320 --> 00:38:35.330 align:start position:0% connection issue rather than waiting 00:38:35.330 --> 00:38:38.380 align:start position:0% connection issue rather than waiting until<00:38:35.660> the<00:38:35.900> site<00:38:36.260> plan<00:38:36.470> to<00:38:36.830> make<00:38:37.010> that<00:38:37.390> earlier 00:38:38.380 --> 00:38:38.390 align:start position:0% until the site plan to make that earlier 00:38:38.390 --> 00:38:42.910 align:start position:0% until the site plan to make that earlier you<00:38:38.840> know<00:38:38.990> based<00:38:39.230> on<00:38:41.350> based<00:38:42.350> on<00:38:42.620> information 00:38:42.910 --> 00:38:42.920 align:start position:0% you know based on based on information 00:38:42.920 --> 00:38:44.620 align:start position:0% you know based on based on information that's<00:38:43.370> available<00:38:43.490> related<00:38:44.000> to<00:38:44.330> wear<00:38:44.480> those 00:38:44.620 --> 00:38:44.630 align:start position:0% that's available related to wear those 00:38:44.630 --> 00:38:47.020 align:start position:0% that's available related to wear those connections<00:38:45.170> would<00:38:45.350> be<00:38:45.500> I<00:38:45.740> guess<00:38:46.730> my<00:38:46.760> other 00:38:47.020 --> 00:38:47.030 align:start position:0% connections would be I guess my other 00:38:47.030 --> 00:38:49.210 align:start position:0% connections would be I guess my other because<00:38:47.630> comment<00:38:47.930> would<00:38:48.200> be<00:38:48.260> and<00:38:48.860> support 00:38:49.210 --> 00:38:49.220 align:start position:0% because comment would be and support 00:38:49.220 --> 00:38:50.500 align:start position:0% because comment would be and support some<00:38:49.370> of<00:38:49.430> the<00:38:49.490> other<00:38:49.610> comments<00:38:50.000> other<00:38:50.270> folks 00:38:50.500 --> 00:38:50.510 align:start position:0% some of the other comments other folks 00:38:50.510 --> 00:38:54.070 align:start position:0% some of the other comments other folks on<00:38:50.960> the<00:38:51.110> board<00:38:51.380> have<00:38:52.000> as<00:38:53.000> we<00:38:53.810> look<00:38:53.960> at 00:38:54.070 --> 00:38:54.080 align:start position:0% on the board have as we look at 00:38:54.080 --> 00:38:55.720 align:start position:0% on the board have as we look at connectivity<00:38:54.710> particularly<00:38:55.130> as<00:38:55.190> we<00:38:55.220> look<00:38:55.520> at 00:38:55.720 --> 00:38:55.730 align:start position:0% connectivity particularly as we look at 00:38:55.730 --> 00:38:59.320 align:start position:0% connectivity particularly as we look at existing<00:38:56.600> residential<00:38:57.790> dynasty<00:38:58.790> or<00:38:58.820> other 00:38:59.320 --> 00:38:59.330 align:start position:0% existing residential dynasty or other 00:38:59.330 --> 00:39:01.720 align:start position:0% existing residential dynasty or other potentially<00:39:00.230> mixed-use<00:39:01.130> development 00:39:01.720 --> 00:39:01.730 align:start position:0% potentially mixed-use development 00:39:01.730 --> 00:39:04.810 align:start position:0% potentially mixed-use development commercial<00:39:02.120> development<00:39:02.630> to<00:39:02.810> be<00:39:03.670> what<00:39:04.670> the 00:39:04.810 --> 00:39:04.820 align:start position:0% commercial development to be what the 00:39:04.820 --> 00:39:06.160 align:start position:0% commercial development to be what the staff<00:39:05.060> can<00:39:05.300> do<00:39:05.420> in<00:39:05.540> terms<00:39:05.750> of<00:39:05.900> is<00:39:06.020> you're 00:39:06.160 --> 00:39:06.170 align:start position:0% staff can do in terms of is you're 00:39:06.170 --> 00:39:09.070 align:start position:0% staff can do in terms of is you're looking<00:39:06.200> at<00:39:06.500> language<00:39:06.710> to<00:39:07.610> identify<00:39:08.420> you<00:39:09.050> know 00:39:09.070 --> 00:39:09.080 align:start position:0% looking at language to identify you know 00:39:09.080 --> 00:39:11.790 align:start position:0% looking at language to identify you know either<00:39:09.760> compatible<00:39:10.760> or<00:39:10.910> incompatible 00:39:11.790 --> 00:39:11.800 align:start position:0% either compatible or incompatible 00:39:11.800 --> 00:39:15.460 align:start position:0% either compatible or incompatible connectivity<00:39:13.540> and<00:39:14.540> exactly<00:39:15.200> what<00:39:15.410> I'm 00:39:15.460 --> 00:39:15.470 align:start position:0% connectivity and exactly what I'm 00:39:15.470 --> 00:39:17.830 align:start position:0% connectivity and exactly what I'm looking<00:39:15.680> for<00:39:15.890> but<00:39:15.920> you<00:39:16.130> know<00:39:16.450> even<00:39:17.450> if<00:39:17.690> it's 00:39:17.830 --> 00:39:17.840 align:start position:0% looking for but you know even if it's 00:39:17.840 --> 00:39:19.330 align:start position:0% looking for but you know even if it's the<00:39:17.960> broad<00:39:18.170> sense<00:39:18.410> what<00:39:18.650> could<00:39:18.920> or<00:39:19.070> couldn't 00:39:19.330 --> 00:39:19.340 align:start position:0% the broad sense what could or couldn't 00:39:19.340 --> 00:39:23.530 align:start position:0% the broad sense what could or couldn't work<00:39:20.410> earlier<00:39:21.410> on<00:39:21.590> the<00:39:21.800> process<00:39:22.280> of<00:39:22.580> you<00:39:23.480> know 00:39:23.530 --> 00:39:23.540 align:start position:0% work earlier on the process of you know 00:39:23.540 --> 00:39:25.630 align:start position:0% work earlier on the process of you know in<00:39:23.750> terms<00:39:23.930> of<00:39:24.110> whether<00:39:24.260> it<00:39:24.350> be<00:39:24.470> rezoning<00:39:24.950> etc 00:39:25.630 --> 00:39:25.640 align:start position:0% in terms of whether it be rezoning etc 00:39:25.640 --> 00:39:27.610 align:start position:0% in terms of whether it be rezoning etc but<00:39:25.940> anything<00:39:26.330> that<00:39:26.360> does<00:39:26.780> you<00:39:27.200> know<00:39:27.320> I<00:39:27.350> think 00:39:27.610 --> 00:39:27.620 align:start position:0% but anything that does you know I think 00:39:27.620 --> 00:39:30.370 align:start position:0% but anything that does you know I think just<00:39:28.400> to<00:39:28.640> so<00:39:28.940> we<00:39:29.090> don't<00:39:29.270> go<00:39:29.390> so<00:39:29.780> far<00:39:29.960> down<00:39:30.020> the 00:39:30.370 --> 00:39:30.380 align:start position:0% just to so we don't go so far down the 00:39:30.380 --> 00:39:35.200 align:start position:0% just to so we don't go so far down the road<00:39:30.770> so<00:39:31.430> to<00:39:31.460> say<00:39:31.790> and<00:39:32.800> for<00:39:33.800> all<00:39:34.550> the<00:39:34.850> issues 00:39:35.200 --> 00:39:35.210 align:start position:0% road so to say and for all the issues 00:39:35.210 --> 00:39:37.780 align:start position:0% road so to say and for all the issues that<00:39:35.240> on<00:39:35.780> for<00:39:36.500> everybody<00:39:36.800> on<00:39:36.860> all<00:39:37.070> sides<00:39:37.610> of 00:39:37.780 --> 00:39:37.790 align:start position:0% that on for everybody on all sides of 00:39:37.790 --> 00:39:39.040 align:start position:0% that on for everybody on all sides of the<00:39:37.880> issue<00:39:37.970> you<00:39:38.390> know<00:39:38.510> just<00:39:38.690> to<00:39:38.840> try<00:39:39.020> to 00:39:39.040 --> 00:39:39.050 align:start position:0% the issue you know just to try to 00:39:39.050 --> 00:39:41.380 align:start position:0% the issue you know just to try to resolve<00:39:39.350> those<00:39:39.590> things<00:39:39.860> then<00:39:40.070> identify<00:39:40.550> what 00:39:41.380 --> 00:39:41.390 align:start position:0% resolve those things then identify what 00:39:41.390 --> 00:39:44.170 align:start position:0% resolve those things then identify what would<00:39:41.570> work<00:39:41.780> what<00:39:42.110> wouldn't<00:39:42.460> and<00:39:43.460> that<00:39:44.000> was 00:39:44.170 --> 00:39:44.180 align:start position:0% would work what wouldn't and that was 00:39:44.180 --> 00:39:46.470 align:start position:0% would work what wouldn't and that was one<00:39:44.660> thing<00:39:44.870> that<00:39:44.930> we're<00:39:45.200> trying<00:39:45.380> to<00:39:45.710> do<00:39:45.890> with 00:39:46.470 --> 00:39:46.480 align:start position:0% one thing that we're trying to do with 00:39:46.480 --> 00:39:49.750 align:start position:0% one thing that we're trying to do with with<00:39:47.480> this<00:39:47.660> ordinance<00:39:48.170> to<00:39:48.530> preserve<00:39:49.280> you<00:39:49.640> know 00:39:49.750 --> 00:39:49.760 align:start position:0% with this ordinance to preserve you know 00:39:49.760 --> 00:39:54.280 align:start position:0% with this ordinance to preserve you know the<00:39:49.970> one<00:39:50.120> hand<00:39:50.450> preserve<00:39:51.400> and<00:39:52.420> to<00:39:53.420> some<00:39:53.870> extent 00:39:54.280 --> 00:39:54.290 align:start position:0% the one hand preserve and to some extent 00:39:54.290 --> 00:39:57.640 align:start position:0% the one hand preserve and to some extent the<00:39:54.610> connectivity<00:39:56.140> provision<00:39:57.140> so<00:39:57.350> that<00:39:57.530> we 00:39:57.640 --> 00:39:57.650 align:start position:0% the connectivity provision so that we 00:39:57.650 --> 00:40:00.640 align:start position:0% the connectivity provision so that we don't<00:39:57.860> and<00:39:58.220> in<00:39:59.210> the<00:39:59.360> long<00:39:59.570> run<00:39:59.600> end<00:40:00.140> up<00:40:00.350> with 00:40:00.640 --> 00:40:00.650 align:start position:0% don't and in the long run end up with 00:40:00.650 --> 00:40:03.670 align:start position:0% don't and in the long run end up with all<00:40:01.550> of<00:40:01.880> our<00:40:02.000> developments<00:40:02.810> being<00:40:03.140> ending<00:40:03.560> in 00:40:03.670 --> 00:40:03.680 align:start position:0% all of our developments being ending in 00:40:03.680 --> 00:40:04.480 align:start position:0% all of our developments being ending in cul-de-sacs<00:40:04.250> and 00:40:04.480 --> 00:40:04.490 align:start position:0% cul-de-sacs and 00:40:04.490 --> 00:40:05.859 align:start position:0% cul-de-sacs and you<00:40:04.520> don't<00:40:04.700> have<00:40:04.940> through<00:40:05.480> connections 00:40:05.859 --> 00:40:05.869 align:start position:0% you don't have through connections 00:40:05.869 --> 00:40:08.290 align:start position:0% you don't have through connections because<00:40:06.230> that<00:40:06.440> that<00:40:06.740> creates<00:40:07.040> problems<00:40:08.000> as 00:40:08.290 --> 00:40:08.300 align:start position:0% because that that creates problems as 00:40:08.300 --> 00:40:11.140 align:start position:0% because that that creates problems as well<00:40:08.330> so<00:40:08.750> this<00:40:08.869> is<00:40:09.080> an<00:40:09.200> attempt<00:40:09.560> to<00:40:09.680> to<00:40:10.580> balance 00:40:11.140 --> 00:40:11.150 align:start position:0% well so this is an attempt to to balance 00:40:11.150 --> 00:40:14.770 align:start position:0% well so this is an attempt to to balance to<00:40:11.960> balance<00:40:12.320> that<00:40:12.530> out<00:40:12.590> a<00:40:13.160> little<00:40:13.730> bit<00:40:14.240> more<00:40:14.510> so 00:40:14.770 --> 00:40:14.780 align:start position:0% to balance that out a little bit more so 00:40:14.780 --> 00:40:18.609 align:start position:0% to balance that out a little bit more so we<00:40:14.810> can<00:40:14.990> to<00:40:15.890> do<00:40:16.400> the<00:40:16.550> extent<00:40:16.970> that<00:40:17.000> we<00:40:17.240> can<00:40:17.619> you 00:40:18.609 --> 00:40:18.619 align:start position:0% we can to do the extent that we can you 00:40:18.619 --> 00:40:20.500 align:start position:0% we can to do the extent that we can you know<00:40:18.740> find<00:40:19.040> that<00:40:19.220> balance<00:40:19.460> and<00:40:19.910> be<00:40:20.030> able<00:40:20.150> to 00:40:20.500 --> 00:40:20.510 align:start position:0% know find that balance and be able to 00:40:20.510 --> 00:40:22.240 align:start position:0% know find that balance and be able to know<00:40:20.690> earlier<00:40:21.170> in<00:40:21.260> the<00:40:21.290> process<00:40:21.560> for<00:40:22.100> those 00:40:22.240 --> 00:40:22.250 align:start position:0% know earlier in the process for those 00:40:22.250 --> 00:40:25.450 align:start position:0% know earlier in the process for those those<00:40:22.880> cases<00:40:23.480> where<00:40:23.750> we<00:40:23.900> can<00:40:24.200> have<00:40:25.190> some 00:40:25.450 --> 00:40:25.460 align:start position:0% those cases where we can have some 00:40:25.460 --> 00:40:28.780 align:start position:0% those cases where we can have some specific<00:40:25.700> criteria<00:40:26.600> and<00:40:26.720> see<00:40:26.960> where<00:40:27.550> how<00:40:28.550> that 00:40:28.780 --> 00:40:28.790 align:start position:0% specific criteria and see where how that 00:40:28.790 --> 00:40:30.160 align:start position:0% specific criteria and see where how that could<00:40:28.970> be<00:40:29.000> addressed<00:40:29.480> to<00:40:29.600> be<00:40:29.720> able<00:40:29.810> to<00:40:29.990> tell 00:40:30.160 --> 00:40:30.170 align:start position:0% could be addressed to be able to tell 00:40:30.170 --> 00:40:32.140 align:start position:0% could be addressed to be able to tell folks<00:40:30.440> earlier<00:40:30.920> in<00:40:31.220> the<00:40:31.250> process<00:40:31.520> how<00:40:31.970> that 00:40:32.140 --> 00:40:32.150 align:start position:0% folks earlier in the process how that 00:40:32.150 --> 00:40:34.900 align:start position:0% folks earlier in the process how that could<00:40:32.420> work<00:40:32.740> as<00:40:33.740> with<00:40:34.010> any<00:40:34.040> you<00:40:34.880> know 00:40:34.900 --> 00:40:34.910 align:start position:0% could work as with any you know 00:40:34.910 --> 00:40:37.270 align:start position:0% could work as with any you know amendment<00:40:35.540> then<00:40:35.750> you<00:40:35.930> think<00:40:36.170> you've<00:40:36.320> had<00:40:37.250> on 00:40:37.270 --> 00:40:37.280 align:start position:0% amendment then you think you've had on 00:40:37.280 --> 00:40:41.470 align:start position:0% amendment then you think you've had on this<00:40:37.520> to<00:40:37.820> that<00:40:38.950> it's<00:40:39.950> not<00:40:40.220> going<00:40:40.460> to<00:40:40.550> resolve 00:40:41.470 --> 00:40:41.480 align:start position:0% this to that it's not going to resolve 00:40:41.480 --> 00:40:43.840 align:start position:0% this to that it's not going to resolve every<00:40:42.050> scenario<00:40:42.619> when<00:40:43.040> at<00:40:43.190> least<00:40:43.340> with<00:40:43.640> this 00:40:43.840 --> 00:40:43.850 align:start position:0% every scenario when at least with this 00:40:43.850 --> 00:40:49.359 align:start position:0% every scenario when at least with this this<00:40:44.810> this<00:40:45.500> first<00:40:46.000> attempt<00:40:47.000> to<00:40:47.270> have<00:40:48.250> you<00:40:49.250> know 00:40:49.359 --> 00:40:49.369 align:start position:0% this this first attempt to have you know 00:40:49.369 --> 00:40:51.130 align:start position:0% this this first attempt to have you know something<00:40:49.910> more<00:40:50.330> solidified<00:40:50.690> in<00:40:51.080> the 00:40:51.130 --> 00:40:51.140 align:start position:0% something more solidified in the 00:40:51.140 --> 00:40:52.660 align:start position:0% something more solidified in the ordinance<00:40:51.530> with<00:40:51.710> this<00:40:51.920> to<00:40:52.130> try<00:40:52.340> to<00:40:52.400> narrow 00:40:52.660 --> 00:40:52.670 align:start position:0% ordinance with this to try to narrow 00:40:52.670 --> 00:40:54.820 align:start position:0% ordinance with this to try to narrow that<00:40:52.880> down<00:40:52.940> to<00:40:53.420> go<00:40:53.540> as<00:40:53.720> far<00:40:53.930> as<00:40:54.050> we<00:40:54.170> can<00:40:54.380> with<00:40:54.650> it 00:40:54.820 --> 00:40:54.830 align:start position:0% that down to go as far as we can with it 00:40:54.830 --> 00:40:56.560 align:start position:0% that down to go as far as we can with it and<00:40:55.010> then<00:40:55.130> over<00:40:55.430> time<00:40:55.610> you<00:40:55.970> know<00:40:56.000> these<00:40:56.270> things 00:40:56.560 --> 00:40:56.570 align:start position:0% and then over time you know these things 00:40:56.570 --> 00:40:58.780 align:start position:0% and then over time you know these things you<00:40:57.050> know<00:40:57.080> often<00:40:57.500> amendments<00:40:58.010> continue<00:40:58.640> to 00:40:58.780 --> 00:40:58.790 align:start position:0% you know often amendments continue to 00:40:58.790 --> 00:41:01.030 align:start position:0% you know often amendments continue to evolve<00:40:59.030> somewhat<00:40:59.540> over<00:40:59.810> time<00:41:00.020> in<00:41:00.290> addressing 00:41:01.030 --> 00:41:01.040 align:start position:0% evolve somewhat over time in addressing 00:41:01.040 --> 00:41:04.660 align:start position:0% evolve somewhat over time in addressing more<00:41:01.400> and<00:41:01.520> more<00:41:02.530> types<00:41:03.530> of<00:41:03.740> situations<00:41:03.980> that 00:41:04.660 --> 00:41:04.670 align:start position:0% more and more types of situations that 00:41:04.670 --> 00:41:06.670 align:start position:0% more and more types of situations that come<00:41:04.880> forward<00:41:05.390> but<00:41:05.630> this<00:41:05.840> is<00:41:06.050> this<00:41:06.380> is<00:41:06.560> an 00:41:06.670 --> 00:41:06.680 align:start position:0% come forward but this is this is an 00:41:06.680 --> 00:41:08.710 align:start position:0% come forward but this is this is an effort<00:41:06.980> to<00:41:07.100> expand<00:41:07.670> our<00:41:07.880> capability<00:41:08.690> to 00:41:08.710 --> 00:41:08.720 align:start position:0% effort to expand our capability to 00:41:08.720 --> 00:41:11.710 align:start position:0% effort to expand our capability to provide<00:41:09.050> the<00:41:09.380> flexibility<00:41:10.100> and<00:41:10.190> it<00:41:10.720> doesn't 00:41:11.710 --> 00:41:11.720 align:start position:0% provide the flexibility and it doesn't 00:41:11.720 --> 00:41:13.930 align:start position:0% provide the flexibility and it doesn't get<00:41:11.900> to<00:41:12.050> everything<00:41:12.590> that<00:41:12.670> everyone<00:41:13.670> would 00:41:13.930 --> 00:41:13.940 align:start position:0% get to everything that everyone would 00:41:13.940 --> 00:41:15.700 align:start position:0% get to everything that everyone would like<00:41:14.119> to<00:41:14.300> see<00:41:14.510> but<00:41:14.720> we<00:41:14.840> feel<00:41:15.050> like<00:41:15.170> it's<00:41:15.410> a<00:41:15.530> good 00:41:15.700 --> 00:41:15.710 align:start position:0% like to see but we feel like it's a good 00:41:15.710 --> 00:41:19.150 align:start position:0% like to see but we feel like it's a good balance<00:41:15.890> that<00:41:16.520> can<00:41:17.080> give<00:41:18.080> us<00:41:18.109> some<00:41:18.290> traction 00:41:19.150 --> 00:41:19.160 align:start position:0% balance that can give us some traction 00:41:19.160 --> 00:41:25.210 align:start position:0% balance that can give us some traction to<00:41:19.520> move<00:41:19.670> in<00:41:19.880> with<00:41:20.150> them<00:41:21.310> Thank<00:41:22.310> You<00:41:24.220> mr. 00:41:25.210 --> 00:41:25.220 align:start position:0% to move in with them Thank You mr. 00:41:25.220 --> 00:41:27.310 align:start position:0% to move in with them Thank You mr. chairman<00:41:25.760> Kuk<00:41:25.970> we<00:41:26.090> fight<00:41:26.270> on<00:41:26.480> this<00:41:26.660> separately 00:41:27.310 --> 00:41:27.320 align:start position:0% chairman Kuk we fight on this separately 00:41:27.320 --> 00:41:29.470 align:start position:0% chairman Kuk we fight on this separately from<00:41:27.740> the<00:41:27.980> other<00:41:28.160> I<00:41:28.580> think<00:41:29.210> that<00:41:29.359> would 00:41:29.470 --> 00:41:29.480 align:start position:0% from the other I think that would 00:41:29.480 --> 00:41:31.480 align:start position:0% from the other I think that would probably<00:41:29.630> be<00:41:29.930> a<00:41:30.020> wise<00:41:30.260> thing<00:41:30.500> 30<00:41:30.800> days<00:41:31.010> or<00:41:31.310> so 00:41:31.480 --> 00:41:31.490 align:start position:0% probably be a wise thing 30 days or so 00:41:31.490 --> 00:41:33.910 align:start position:0% probably be a wise thing 30 days or so out<00:41:31.970> of<00:41:32.000> the<00:41:32.119> way<00:41:32.240> and<00:41:32.510> you<00:41:32.660> know<00:41:32.720> yeah<00:41:33.230> if 00:41:33.910 --> 00:41:33.920 align:start position:0% out of the way and you know yeah if 00:41:33.920 --> 00:41:36.609 align:start position:0% out of the way and you know yeah if there's<00:41:34.780> are<00:41:35.780> there<00:41:35.930> any<00:41:36.050> other<00:41:36.200> questions<00:41:36.230> I 00:41:36.609 --> 00:41:36.619 align:start position:0% there's are there any other questions I 00:41:36.619 --> 00:41:38.859 align:start position:0% there's are there any other questions I just<00:41:36.920> have<00:41:37.040> one<00:41:37.250> last<00:41:37.460> one<00:41:37.820> if<00:41:38.240> there<00:41:38.750> aren't 00:41:38.859 --> 00:41:38.869 align:start position:0% just have one last one if there aren't 00:41:38.869 --> 00:41:44.890 align:start position:0% just have one last one if there aren't any<00:41:39.080> more<00:41:39.430> and<00:41:40.430> that's<00:41:40.640> about<00:41:40.880> the<00:41:43.900> the 00:41:44.890 --> 00:41:44.900 align:start position:0% any more and that's about the the 00:41:44.900 --> 00:41:47.560 align:start position:0% any more and that's about the the establishment<00:41:45.650> of<00:41:45.770> a<00:41:46.310> condition<00:41:47.240> someone 00:41:47.560 --> 00:41:47.570 align:start position:0% establishment of a condition someone 00:41:47.570 --> 00:41:49.120 align:start position:0% establishment of a condition someone puts<00:41:47.780> a<00:41:47.869> zoning<00:41:48.200> condition<00:41:48.619> forward 00:41:49.120 --> 00:41:49.130 align:start position:0% puts a zoning condition forward 00:41:49.130 --> 00:41:51.040 align:start position:0% puts a zoning condition forward especially<00:41:49.700> for<00:41:50.240> like<00:41:50.420> the<00:41:50.570> emergency 00:41:51.040 --> 00:41:51.050 align:start position:0% especially for like the emergency 00:41:51.050 --> 00:41:53.859 align:start position:0% especially for like the emergency vehicle<00:41:51.410> access<00:41:51.740> or<00:41:51.920> something<00:41:52.480> that's<00:41:53.480> just 00:41:53.859 --> 00:41:53.869 align:start position:0% vehicle access or something that's just 00:41:53.869 --> 00:41:55.480 align:start position:0% vehicle access or something that's just the<00:41:54.050> condition<00:41:54.500> there<00:41:54.740> doesn't<00:41:54.920> have<00:41:55.070> to<00:41:55.190> be<00:41:55.369> a 00:41:55.480 --> 00:41:55.490 align:start position:0% the condition there doesn't have to be a 00:41:55.490 --> 00:41:57.940 align:start position:0% the condition there doesn't have to be a detailed<00:41:56.359> breakdown<00:41:56.630> at<00:41:57.050> that<00:41:57.230> point<00:41:57.560> of<00:41:57.740> how 00:41:57.940 --> 00:41:57.950 align:start position:0% detailed breakdown at that point of how 00:41:57.950 --> 00:41:59.830 align:start position:0% detailed breakdown at that point of how that<00:41:58.010> is<00:41:58.430> going<00:41:58.490> to<00:41:58.790> be<00:41:58.910> achieved<00:41:59.030> just<00:41:59.630> like 00:41:59.830 --> 00:41:59.840 align:start position:0% that is going to be achieved just like 00:41:59.840 --> 00:42:02.830 align:start position:0% that is going to be achieved just like in<00:42:00.830> our<00:42:00.950> regular<00:42:01.310> process<00:42:01.609> correct<00:42:02.270> you<00:42:02.450> they 00:42:02.830 --> 00:42:02.840 align:start position:0% in our regular process correct you they 00:42:02.840 --> 00:42:04.540 align:start position:0% in our regular process correct you they wouldn't<00:42:03.050> have<00:42:03.200> to<00:42:03.260> lay<00:42:03.530> that<00:42:03.740> all<00:42:03.920> out<00:42:04.160> before 00:42:04.540 --> 00:42:04.550 align:start position:0% wouldn't have to lay that all out before 00:42:04.550 --> 00:42:07.270 align:start position:0% wouldn't have to lay that all out before they<00:42:04.670> they<00:42:05.330> come<00:42:05.540> in<00:42:05.690> with<00:42:05.869> I<00:42:06.140> think<00:42:07.040> it's 00:42:07.270 --> 00:42:07.280 align:start position:0% they they come in with I think it's 00:42:07.280 --> 00:42:09.760 align:start position:0% they they come in with I think it's because<00:42:07.540> zoning<00:42:08.540> conditions<00:42:09.050> are<00:42:09.200> voluntary 00:42:09.760 --> 00:42:09.770 align:start position:0% because zoning conditions are voluntary 00:42:09.770 --> 00:42:13.150 align:start position:0% because zoning conditions are voluntary so<00:42:10.570> people<00:42:11.570> could<00:42:11.780> be<00:42:11.960> as<00:42:12.109> detailed<00:42:12.440> and 00:42:13.150 --> 00:42:13.160 align:start position:0% so people could be as detailed and 00:42:13.160 --> 00:42:15.609 align:start position:0% so people could be as detailed and specific<00:42:13.550> with<00:42:14.210> that<00:42:14.390> as<00:42:14.540> they<00:42:14.780> chose<00:42:15.260> to<00:42:15.290> be 00:42:15.609 --> 00:42:15.619 align:start position:0% specific with that as they chose to be 00:42:15.619 --> 00:42:16.730 align:start position:0% specific with that as they chose to be in<00:42:15.710> some<00:42:15.980> cases 00:42:16.730 --> 00:42:16.740 align:start position:0% in some cases 00:42:16.740 --> 00:42:29.450 align:start position:0% in some cases it<00:42:17.160> may<00:42:17.550> be<00:42:22.760> soon<00:42:26.540> in<00:42:27.540> a<00:42:27.780> two<00:42:27.990> tier<00:42:28.290> 2<00:42:28.560> is<00:42:29.220> just 00:42:29.450 --> 00:42:29.460 align:start position:0% it may be soon in a two tier 2 is just 00:42:29.460 --> 00:42:32.390 align:start position:0% it may be soon in a two tier 2 is just taking<00:42:30.150> an<00:42:30.240> example<00:42:30.780> you<00:42:31.260> could<00:42:31.530> have<00:42:31.890> a 00:42:32.390 --> 00:42:32.400 align:start position:0% taking an example you could have a 00:42:32.400 --> 00:42:34.730 align:start position:0% taking an example you could have a zoning<00:42:33.119> condition<00:42:33.690> that<00:42:33.900> said<00:42:34.230> that<00:42:34.260> you 00:42:34.730 --> 00:42:34.740 align:start position:0% zoning condition that said that you 00:42:34.740 --> 00:42:37.850 align:start position:0% zoning condition that said that you would<00:42:34.920> not<00:42:35.100> provide<00:42:35.520> a<00:42:35.580> full<00:42:36.680> public<00:42:37.680> road 00:42:37.850 --> 00:42:37.860 align:start position:0% would not provide a full public road 00:42:37.860 --> 00:42:39.620 align:start position:0% would not provide a full public road connection<00:42:38.340> because<00:42:38.670> in<00:42:38.820> tier<00:42:39.030> 2<00:42:39.240> that's<00:42:39.480> a 00:42:39.620 --> 00:42:39.630 align:start position:0% connection because in tier 2 that's a 00:42:39.630 --> 00:42:42.410 align:start position:0% connection because in tier 2 that's a possibility<00:42:40.080> would<00:42:40.650> not<00:42:40.860> be<00:42:41.130> possible<00:42:41.880> into 00:42:42.410 --> 00:42:42.420 align:start position:0% possibility would not be possible into 00:42:42.420 --> 00:42:45.320 align:start position:0% possibility would not be possible into your<00:42:42.540> one<00:42:42.720> to<00:42:43.110> do<00:42:43.290> that<00:42:43.320> but<00:42:44.280> in<00:42:44.460> tier<00:42:44.700> in<00:42:45.000> tier 00:42:45.320 --> 00:42:45.330 align:start position:0% your one to do that but in tier in tier 00:42:45.330 --> 00:42:48.050 align:start position:0% your one to do that but in tier in tier 2<00:42:45.510> or<00:42:45.690> 3<00:42:45.869> you<00:42:46.020> could<00:42:46.320> you<00:42:47.250> could<00:42:47.490> offer<00:42:47.730> that<00:42:48.030> as 00:42:48.050 --> 00:42:48.060 align:start position:0% 2 or 3 you could you could offer that as 00:42:48.060 --> 00:42:51.650 align:start position:0% 2 or 3 you could you could offer that as a<00:42:48.210> condition<00:42:48.480> and<00:42:49.080> then<00:42:50.150> likewise<00:42:51.150> if<00:42:51.420> you 00:42:51.650 --> 00:42:51.660 align:start position:0% a condition and then likewise if you 00:42:51.660 --> 00:42:59.830 align:start position:0% a condition and then likewise if you were<00:42:52.250> in<00:42:53.250> tier<00:42:53.640> in<00:42:54.030> tier<00:42:54.390> 3<00:42:54.840> you<00:42:55.290> could<00:42:57.350> provide 00:42:59.830 --> 00:42:59.840 align:start position:0% were in tier in tier 3 you could provide 00:42:59.840 --> 00:43:03.020 align:start position:0% were in tier in tier 3 you could provide emergency<00:43:00.980> vehicle<00:43:01.980> access<00:43:02.369> as<00:43:02.580> a<00:43:02.610> zoning 00:43:03.020 --> 00:43:03.030 align:start position:0% emergency vehicle access as a zoning 00:43:03.030 --> 00:43:04.700 align:start position:0% emergency vehicle access as a zoning condition<00:43:03.720> if<00:43:03.900> you<00:43:04.020> wanted<00:43:04.350> to<00:43:04.470> it<00:43:04.560> wouldn't 00:43:04.700 --> 00:43:04.710 align:start position:0% condition if you wanted to it wouldn't 00:43:04.710 --> 00:43:07.910 align:start position:0% condition if you wanted to it wouldn't be<00:43:04.830> required<00:43:05.220> in<00:43:05.550> that<00:43:06.090> tier<00:43:06.420> but<00:43:06.690> if<00:43:06.900> if<00:43:07.740> the 00:43:07.910 --> 00:43:07.920 align:start position:0% be required in that tier but if if the 00:43:07.920 --> 00:43:13.990 align:start position:0% be required in that tier but if if the adjacent<00:43:08.730> neighborhood<00:43:09.150> for<00:43:09.330> example<00:43:11.510> and 00:43:13.990 --> 00:43:14.000 align:start position:0% adjacent neighborhood for example and 00:43:14.000 --> 00:43:17.480 align:start position:0% adjacent neighborhood for example and wanted<00:43:15.000> to<00:43:15.150> have<00:43:15.500> some<00:43:16.500> sort<00:43:16.740> of<00:43:16.950> connection 00:43:17.480 --> 00:43:17.490 align:start position:0% wanted to have some sort of connection 00:43:17.490 --> 00:43:19.880 align:start position:0% wanted to have some sort of connection or<00:43:17.820> for<00:43:18.000> some<00:43:18.240> for<00:43:18.780> some<00:43:18.810> reason<00:43:19.410> that<00:43:19.560> seemed 00:43:19.880 --> 00:43:19.890 align:start position:0% or for some for some reason that seemed 00:43:19.890 --> 00:43:21.980 align:start position:0% or for some for some reason that seemed desirable<00:43:20.430> but<00:43:20.790> it<00:43:20.910> wasn't<00:43:21.270> required<00:43:21.480> you 00:43:21.980 --> 00:43:21.990 align:start position:0% desirable but it wasn't required you 00:43:21.990 --> 00:43:24.200 align:start position:0% desirable but it wasn't required you could<00:43:22.260> voluntarily<00:43:23.190> offer<00:43:23.609> to<00:43:23.910> do<00:43:24.030> that 00:43:24.200 --> 00:43:24.210 align:start position:0% could voluntarily offer to do that 00:43:24.210 --> 00:43:26.240 align:start position:0% could voluntarily offer to do that anyway<00:43:24.480> so<00:43:25.170> there's<00:43:25.410> a<00:43:25.470> lot<00:43:25.680> of<00:43:25.740> different 00:43:26.240 --> 00:43:26.250 align:start position:0% anyway so there's a lot of different 00:43:26.250 --> 00:43:29.750 align:start position:0% anyway so there's a lot of different permutations<00:43:26.580> of<00:43:27.330> how<00:43:28.250> zoning<00:43:29.250> conditions 00:43:29.750 --> 00:43:29.760 align:start position:0% permutations of how zoning conditions 00:43:29.760 --> 00:43:31.880 align:start position:0% permutations of how zoning conditions could<00:43:30.000> be<00:43:30.150> offered<00:43:30.570> with<00:43:30.750> the<00:43:30.900> key<00:43:31.080> being<00:43:31.440> at 00:43:31.880 --> 00:43:31.890 align:start position:0% could be offered with the key being at 00:43:31.890 --> 00:43:35.210 align:start position:0% could be offered with the key being at any<00:43:32.720> for<00:43:33.720> any<00:43:33.869> particular<00:43:34.170> scenario<00:43:35.040> you<00:43:35.190> just 00:43:35.210 --> 00:43:35.220 align:start position:0% any for any particular scenario you just 00:43:35.220 --> 00:43:36.859 align:start position:0% any for any particular scenario you just would<00:43:35.609> have<00:43:35.730> to<00:43:35.910> make<00:43:36.090> sure<00:43:36.300> that<00:43:36.630> it's 00:43:36.859 --> 00:43:36.869 align:start position:0% would have to make sure that it's 00:43:36.869 --> 00:43:38.900 align:start position:0% would have to make sure that it's something<00:43:37.170> that's<00:43:37.530> more<00:43:38.130> restrictive<00:43:38.910> than 00:43:38.900 --> 00:43:38.910 align:start position:0% something that's more restrictive than 00:43:38.910 --> 00:43:41.420 align:start position:0% something that's more restrictive than what<00:43:39.720> your<00:43:40.200> tier<00:43:40.470> would<00:43:40.680> otherwise<00:43:41.040> allowed 00:43:41.420 --> 00:43:41.430 align:start position:0% what your tier would otherwise allowed 00:43:41.430 --> 00:43:45.260 align:start position:0% what your tier would otherwise allowed and<00:43:41.700> then<00:43:42.180> within<00:43:42.450> that<00:43:43.070> the<00:43:44.070> it's<00:43:44.550> up<00:43:44.880> to<00:43:45.090> the 00:43:45.260 --> 00:43:45.270 align:start position:0% and then within that the it's up to the 00:43:45.270 --> 00:43:49.130 align:start position:0% and then within that the it's up to the applicant<00:43:46.080> to<00:43:47.300> propose<00:43:48.300> a<00:43:48.330> condition<00:43:48.960> because 00:43:49.130 --> 00:43:49.140 align:start position:0% applicant to propose a condition because 00:43:49.140 --> 00:43:50.900 align:start position:0% applicant to propose a condition because their<00:43:49.290> voluntary<00:43:49.770> and<00:43:50.130> then<00:43:50.250> staff<00:43:50.580> always 00:43:50.900 --> 00:43:50.910 align:start position:0% their voluntary and then staff always 00:43:50.910 --> 00:43:52.820 align:start position:0% their voluntary and then staff always refuse<00:43:51.540> those<00:43:51.780> to<00:43:52.109> make<00:43:52.290> sure<00:43:52.500> that<00:43:52.710> it's 00:43:52.820 --> 00:43:52.830 align:start position:0% refuse those to make sure that it's 00:43:52.830 --> 00:43:55.310 align:start position:0% refuse those to make sure that it's something<00:43:53.100> reasonable<00:43:53.880> is<00:43:54.140> related<00:43:55.140> to<00:43:55.290> the 00:43:55.310 --> 00:43:55.320 align:start position:0% something reasonable is related to the 00:43:55.320 --> 00:43:57.260 align:start position:0% something reasonable is related to the impacts<00:43:55.770> of<00:43:56.010> the<00:43:56.130> development<00:43:56.730> so<00:43:56.880> it's<00:43:57.090> a 00:43:57.260 --> 00:43:57.270 align:start position:0% impacts of the development so it's a 00:43:57.270 --> 00:44:00.290 align:start position:0% impacts of the development so it's a condition<00:43:57.930> that<00:43:58.230> we<00:43:58.440> can<00:43:58.619> legally<00:43:59.070> accept<00:43:59.609> or 00:44:00.290 --> 00:44:00.300 align:start position:0% condition that we can legally accept or 00:44:00.300 --> 00:44:04.670 align:start position:0% condition that we can legally accept or consider<00:44:02.000> thank<00:44:03.000> you<00:44:03.380> we<00:44:04.380> have<00:44:04.500> any<00:44:04.650> other 00:44:04.670 --> 00:44:04.680 align:start position:0% consider thank you we have any other 00:44:04.680 --> 00:44:10.140 align:start position:0% consider thank you we have any other questions<00:44:05.420> for<00:44:06.420> the<00:44:06.540> moment<00:44:07.190> yes 00:44:10.140 --> 00:44:10.150 align:start position:0% questions for the moment yes 00:44:10.150 --> 00:44:12.870 align:start position:0% questions for the moment yes and<00:44:10.750> this<00:44:11.079> this<00:44:11.109> question<00:44:11.950> might<00:44:12.099> not<00:44:12.700> be 00:44:12.870 --> 00:44:12.880 align:start position:0% and this this question might not be 00:44:12.880 --> 00:44:14.819 align:start position:0% and this this question might not be actual<00:44:13.210> or<00:44:13.270> not<00:44:13.480> but<00:44:13.720> is<00:44:14.440> there<00:44:14.500> any<00:44:14.680> way<00:44:14.799> to 00:44:14.819 --> 00:44:14.829 align:start position:0% actual or not but is there any way to 00:44:14.829 --> 00:44:16.740 align:start position:0% actual or not but is there any way to standardize<00:44:15.430> connectivity<00:44:16.210> is<00:44:16.539> there 00:44:16.740 --> 00:44:16.750 align:start position:0% standardize connectivity is there 00:44:16.750 --> 00:44:21.210 align:start position:0% standardize connectivity is there anything<00:44:16.960> similar<00:44:17.500> to<00:44:17.559> like<00:44:19.950> you<00:44:20.950> know<00:44:21.010> we 00:44:21.210 --> 00:44:21.220 align:start position:0% anything similar to like you know we 00:44:21.220 --> 00:44:23.370 align:start position:0% anything similar to like you know we have<00:44:21.369> traffic<00:44:21.670> issues<00:44:22.150> so<00:44:22.420> we<00:44:22.660> look<00:44:22.900> at<00:44:23.020> a<00:44:23.049> TI<00:44:23.289> a 00:44:23.370 --> 00:44:23.380 align:start position:0% have traffic issues so we look at a TI a 00:44:23.380 --> 00:44:25.349 align:start position:0% have traffic issues so we look at a TI a and<00:44:23.799> there's<00:44:23.950> some<00:44:24.190> guidance<00:44:25.089> through 00:44:25.349 --> 00:44:25.359 align:start position:0% and there's some guidance through 00:44:25.359 --> 00:44:26.970 align:start position:0% and there's some guidance through guidelines<00:44:25.839> that<00:44:25.990> go<00:44:26.260> with<00:44:26.440> that<00:44:26.500> is<00:44:26.859> there 00:44:26.970 --> 00:44:26.980 align:start position:0% guidelines that go with that is there 00:44:26.980 --> 00:44:28.710 align:start position:0% guidelines that go with that is there anything<00:44:27.250> for<00:44:27.549> connectivity<00:44:27.970> out<00:44:28.329> there<00:44:28.539> that 00:44:28.710 --> 00:44:28.720 align:start position:0% anything for connectivity out there that 00:44:28.720 --> 00:44:32.880 align:start position:0% anything for connectivity out there that was<00:44:28.900> referenced<00:44:29.740> we<00:44:29.890> used<00:44:30.190> to<00:44:31.859> propose<00:44:32.859> to 00:44:32.880 --> 00:44:32.890 align:start position:0% was referenced we used to propose to 00:44:32.890 --> 00:44:35.880 align:start position:0% was referenced we used to propose to connectivity<00:44:33.430> changes<00:44:33.990> I<00:44:34.990> think<00:44:35.440> with<00:44:35.619> what 00:44:35.880 --> 00:44:35.890 align:start position:0% connectivity changes I think with what 00:44:35.890 --> 00:44:38.010 align:start position:0% connectivity changes I think with what we're<00:44:36.160> with<00:44:36.760> what<00:44:36.970> we're<00:44:37.150> proposing<00:44:37.480> it's 00:44:38.010 --> 00:44:38.020 align:start position:0% we're with what we're proposing it's 00:44:38.020 --> 00:44:42.960 align:start position:0% we're with what we're proposing it's looking<00:44:38.440> uniquely<00:44:39.039> at<00:44:39.369> the<00:44:41.730> types<00:44:42.730> of 00:44:42.960 --> 00:44:42.970 align:start position:0% looking uniquely at the types of 00:44:42.970 --> 00:44:45.870 align:start position:0% looking uniquely at the types of circumstances<00:44:43.869> that<00:44:43.930> we<00:44:44.170> have<00:44:44.349> here<00:44:44.619> what<00:44:44.890> the 00:44:45.870 --> 00:44:45.880 align:start position:0% circumstances that we have here what the 00:44:45.880 --> 00:44:49.470 align:start position:0% circumstances that we have here what the concerns<00:44:46.390> were<00:44:47.020> that<00:44:47.049> were<00:44:47.410> generated<00:44:48.480> by 00:44:49.470 --> 00:44:49.480 align:start position:0% concerns were that were generated by 00:44:49.480 --> 00:44:53.130 align:start position:0% concerns were that were generated by neighborhood<00:44:50.170> residents<00:44:52.140> concerns 00:44:53.130 --> 00:44:53.140 align:start position:0% neighborhood residents concerns 00:44:53.140 --> 00:44:55.319 align:start position:0% neighborhood residents concerns expressed<00:44:53.380> by<00:44:53.770> counsel<00:44:54.369> to<00:44:54.549> try<00:44:54.760> to<00:44:54.819> find<00:44:55.180> a 00:44:55.319 --> 00:44:55.329 align:start position:0% expressed by counsel to try to find a 00:44:55.329 --> 00:44:58.289 align:start position:0% expressed by counsel to try to find a way<00:44:55.480> to<00:44:55.539> a<00:44:56.260> creative<00:44:57.250> way<00:44:57.400> to<00:44:57.430> address<00:44:58.000> those 00:44:58.289 --> 00:44:58.299 align:start position:0% way to a creative way to address those 00:44:58.299 --> 00:45:10.200 align:start position:0% way to a creative way to address those concerns<00:45:03.299> any<00:45:04.299> other<00:45:04.420> questions<00:45:07.529> so<00:45:09.059> we<00:45:10.059> have 00:45:10.200 --> 00:45:10.210 align:start position:0% concerns any other questions so we have 00:45:10.210 --> 00:45:12.599 align:start position:0% concerns any other questions so we have a<00:45:10.240> little<00:45:10.480> discussion<00:45:10.599> here<00:45:11.109> about<00:45:11.609> possibly 00:45:12.599 --> 00:45:12.609 align:start position:0% a little discussion here about possibly 00:45:12.609 --> 00:45:15.029 align:start position:0% a little discussion here about possibly going<00:45:12.789> back<00:45:13.119> and<00:45:13.299> getting<00:45:13.630> some<00:45:14.039> refinements 00:45:15.029 --> 00:45:15.039 align:start position:0% going back and getting some refinements 00:45:15.039 --> 00:45:20.309 align:start position:0% going back and getting some refinements in<00:45:15.990> this<00:45:17.760> well<00:45:18.760> my<00:45:18.910> plan<00:45:19.329> was<00:45:19.359> to<00:45:19.660> just<00:45:19.869> vote 00:45:20.309 --> 00:45:20.319 align:start position:0% in this well my plan was to just vote 00:45:20.319 --> 00:45:21.900 align:start position:0% in this well my plan was to just vote against<00:45:20.859> it<00:45:20.980> so<00:45:21.190> it<00:45:21.309> would<00:45:21.430> be<00:45:21.549> on<00:45:21.670> the<00:45:21.819> agenda 00:45:21.900 --> 00:45:21.910 align:start position:0% against it so it would be on the agenda 00:45:21.910 --> 00:45:24.720 align:start position:0% against it so it would be on the agenda because<00:45:22.680> unless<00:45:23.680> you<00:45:23.859> think<00:45:23.980> we<00:45:24.160> can<00:45:24.339> send<00:45:24.640> it 00:45:24.720 --> 00:45:24.730 align:start position:0% because unless you think we can send it 00:45:24.730 --> 00:45:26.099 align:start position:0% because unless you think we can send it back<00:45:24.880> I<00:45:25.119> don't<00:45:25.270> think<00:45:25.450> that<00:45:25.510> would<00:45:25.690> be<00:45:25.839> a<00:45:25.869> real 00:45:26.099 --> 00:45:26.109 align:start position:0% back I don't think that would be a real 00:45:26.109 --> 00:45:28.289 align:start position:0% back I don't think that would be a real popular<00:45:26.349> movement<00:45:27.099> oh<00:45:27.160> all<00:45:27.700> these<00:45:27.940> things<00:45:28.180> are 00:45:28.289 --> 00:45:28.299 align:start position:0% popular movement oh all these things are 00:45:28.299 --> 00:45:31.019 align:start position:0% popular movement oh all these things are goodness<00:45:28.750> all<00:45:29.529> of<00:45:29.710> this<00:45:29.859> is<00:45:30.069> good<00:45:30.369> it<00:45:30.730> just 00:45:31.019 --> 00:45:31.029 align:start position:0% goodness all of this is good it just 00:45:31.029 --> 00:45:32.730 align:start position:0% goodness all of this is good it just seems<00:45:31.299> to<00:45:31.480> be<00:45:31.510> missing<00:45:31.779> one<00:45:32.049> thing<00:45:32.260> that 00:45:32.730 --> 00:45:32.740 align:start position:0% seems to be missing one thing that 00:45:32.740 --> 00:45:34.710 align:start position:0% seems to be missing one thing that protects<00:45:33.190> and<00:45:33.460> and<00:45:33.910> I<00:45:34.059> know<00:45:34.119> the<00:45:34.329> intent<00:45:34.660> was 00:45:34.710 --> 00:45:34.720 align:start position:0% protects and and I know the intent was 00:45:34.720 --> 00:45:37.200 align:start position:0% protects and and I know the intent was to<00:45:34.839> protect<00:45:35.289> older<00:45:35.710> neighborhoods<00:45:36.279> but<00:45:37.180> I 00:45:37.200 --> 00:45:37.210 align:start position:0% to protect older neighborhoods but I 00:45:37.210 --> 00:45:39.690 align:start position:0% to protect older neighborhoods but I think<00:45:37.329> this<00:45:37.779> is<00:45:37.839> an<00:45:38.140> opportunity<00:45:38.500> to<00:45:39.250> build<00:45:39.490> in 00:45:39.690 --> 00:45:39.700 align:start position:0% think this is an opportunity to build in 00:45:39.700 --> 00:45:41.460 align:start position:0% think this is an opportunity to build in something<00:45:40.210> that<00:45:40.240> protects<00:45:40.839> the<00:45:41.140> tier<00:45:41.380> 1 00:45:41.460 --> 00:45:41.470 align:start position:0% something that protects the tier 1 00:45:41.470 --> 00:45:45.750 align:start position:0% something that protects the tier 1 neighborhoods<00:45:42.569> from<00:45:43.569> things<00:45:44.109> you<00:45:44.529> know<00:45:45.460> so 00:45:45.750 --> 00:45:45.760 align:start position:0% neighborhoods from things you know so 00:45:45.760 --> 00:45:48.690 align:start position:0% neighborhoods from things you know so that<00:45:45.789> these<00:45:46.180> connectivity<00:45:47.170> issues<00:45:47.680> can<00:45:48.549> be 00:45:48.690 --> 00:45:48.700 align:start position:0% that these connectivity issues can be 00:45:48.700 --> 00:45:51.329 align:start position:0% that these connectivity issues can be looked<00:45:48.940> at<00:45:49.180> at<00:45:49.480> rezoning<00:45:50.020> if<00:45:50.440> the<00:45:50.770> adjacent 00:45:51.329 --> 00:45:51.339 align:start position:0% looked at at rezoning if the adjacent 00:45:51.339 --> 00:45:54.809 align:start position:0% looked at at rezoning if the adjacent use<00:45:51.579> is<00:45:51.849> not<00:45:52.569> residential<00:45:53.440> and<00:45:54.339> I<00:45:54.460> think<00:45:54.700> that 00:45:54.809 --> 00:45:54.819 align:start position:0% use is not residential and I think that 00:45:54.819 --> 00:45:56.400 align:start position:0% use is not residential and I think that would<00:45:54.910> be<00:45:55.029> a<00:45:55.059> good<00:45:55.240> thing<00:45:55.299> to<00:45:55.480> build<00:45:55.809> into<00:45:56.170> here 00:45:56.400 --> 00:45:56.410 align:start position:0% would be a good thing to build into here 00:45:56.410 --> 00:46:00.210 align:start position:0% would be a good thing to build into here so<00:45:56.680> we<00:45:57.220> can<00:45:57.369> either<00:45:57.520> I<00:45:58.980> don't<00:45:59.980> know<00:46:00.069> what<00:46:00.190> our 00:46:00.210 --> 00:46:00.220 align:start position:0% so we can either I don't know what our 00:46:00.220 --> 00:46:02.490 align:start position:0% so we can either I don't know what our options<00:46:00.309> are<00:46:00.880> other<00:46:01.150> than<00:46:01.420> to<00:46:01.599> vote<00:46:01.809> on<00:46:02.049> it<00:46:02.289> and 00:46:02.490 --> 00:46:02.500 align:start position:0% options are other than to vote on it and 00:46:02.500 --> 00:46:05.990 align:start position:0% options are other than to vote on it and and<00:46:02.799> assuming<00:46:03.609> that<00:46:03.789> it's<00:46:03.970> a<00:46:04.119> able<00:46:04.450> to<00:46:05.020> go 00:46:05.990 --> 00:46:06.000 align:start position:0% and assuming that it's a able to go 00:46:06.000 --> 00:46:10.170 align:start position:0% and assuming that it's a able to go fight<00:46:07.000> if<00:46:07.569> I<00:46:07.809> can<00:46:08.079> just<00:46:08.440> offer<00:46:08.829> a<00:46:09.039> comment<00:46:10.029> if 00:46:10.170 --> 00:46:10.180 align:start position:0% fight if I can just offer a comment if 00:46:10.180 --> 00:46:12.510 align:start position:0% fight if I can just offer a comment if there<00:46:10.390> if<00:46:10.720> there<00:46:11.109> are<00:46:11.680> you<00:46:12.220> know<00:46:12.309> any 00:46:12.510 --> 00:46:12.520 align:start position:0% there if there are you know any 00:46:12.520 --> 00:46:15.420 align:start position:0% there if there are you know any significant<00:46:13.680> changes<00:46:14.680> would<00:46:14.950> have<00:46:15.130> to<00:46:15.279> be 00:46:15.420 --> 00:46:15.430 align:start position:0% significant changes would have to be 00:46:15.430 --> 00:46:17.220 align:start position:0% significant changes would have to be reconsidered<00:46:16.180> through<00:46:16.539> the<00:46:16.750> public<00:46:17.049> hearing 00:46:17.220 --> 00:46:17.230 align:start position:0% reconsidered through the public hearing 00:46:17.230 --> 00:46:20.039 align:start position:0% reconsidered through the public hearing process<00:46:17.380> and<00:46:18.250> start<00:46:18.670> over<00:46:18.849> if<00:46:19.210> there<00:46:19.869> are 00:46:20.039 --> 00:46:20.049 align:start position:0% process and start over if there are 00:46:20.049 --> 00:46:22.079 align:start position:0% process and start over if there are concerns<00:46:20.589> one<00:46:20.859> option<00:46:21.369> that<00:46:21.520> you<00:46:21.549> could<00:46:21.730> have 00:46:22.079 --> 00:46:22.089 align:start position:0% concerns one option that you could have 00:46:22.089 --> 00:46:23.109 align:start position:0% concerns one option that you could have would<00:46:22.299> be<00:46:22.359> too 00:46:23.109 --> 00:46:23.119 align:start position:0% would be too 00:46:23.119 --> 00:46:26.109 align:start position:0% would be too vote<00:46:23.420> on<00:46:23.660> what's<00:46:23.960> before<00:46:24.349> you<00:46:24.559> either<00:46:24.940> up<00:46:25.940> or 00:46:26.109 --> 00:46:26.119 align:start position:0% vote on what's before you either up or 00:46:26.119 --> 00:46:30.839 align:start position:0% vote on what's before you either up or down<00:46:26.180> to<00:46:26.470> two<00:46:27.470> how<00:46:27.829> you<00:46:28.210> see<00:46:29.210> that<00:46:29.450> and<00:46:29.720> then 00:46:30.839 --> 00:46:30.849 align:start position:0% down to two how you see that and then 00:46:30.849 --> 00:46:34.120 align:start position:0% down to two how you see that and then send<00:46:31.849> ford<00:46:32.150> also<00:46:32.450> any<00:46:32.990> comments<00:46:33.769> if<00:46:33.890> there's 00:46:34.120 --> 00:46:34.130 align:start position:0% send ford also any comments if there's 00:46:34.130 --> 00:46:36.309 align:start position:0% send ford also any comments if there's areas<00:46:34.579> that<00:46:34.819> you<00:46:34.970> you<00:46:35.450> know<00:46:35.569> feel<00:46:35.839> like<00:46:36.079> it's 00:46:36.309 --> 00:46:36.319 align:start position:0% areas that you you know feel like it's 00:46:36.319 --> 00:46:39.839 align:start position:0% areas that you you know feel like it's deficient<00:46:36.920> or<00:46:36.980> could<00:46:37.220> go<00:46:37.369> farther<00:46:37.700> you<00:46:38.420> could 00:46:39.839 --> 00:46:39.849 align:start position:0% deficient or could go farther you could 00:46:39.849 --> 00:46:42.279 align:start position:0% deficient or could go farther you could state<00:46:40.849> that<00:46:41.119> and<00:46:41.359> bring<00:46:41.509> that<00:46:41.569> forward<00:46:42.049> as 00:46:42.279 --> 00:46:42.289 align:start position:0% state that and bring that forward as 00:46:42.289 --> 00:46:45.059 align:start position:0% state that and bring that forward as information<00:46:42.950> for<00:46:43.190> council<00:46:43.670> to<00:46:44.089> consider<00:46:44.390> as 00:46:45.059 --> 00:46:45.069 align:start position:0% information for council to consider as 00:46:45.069 --> 00:46:48.700 align:start position:0% information for council to consider as as<00:46:46.069> part<00:46:46.970> of<00:46:47.059> your<00:46:47.269> deliberation<00:46:48.140> and<00:46:48.289> making 00:46:48.700 --> 00:46:48.710 align:start position:0% as part of your deliberation and making 00:46:48.710 --> 00:46:53.140 align:start position:0% as part of your deliberation and making your<00:46:50.740> recommendation<00:46:51.759> he<00:46:52.759> could<00:46:52.970> come 00:46:53.140 --> 00:46:53.150 align:start position:0% your recommendation he could come 00:46:53.150 --> 00:46:55.180 align:start position:0% your recommendation he could come forward<00:46:53.599> and<00:46:53.690> another<00:46:54.049> round<00:46:54.349> it's<00:46:54.619> just<00:46:54.920> kind 00:46:55.180 --> 00:46:55.190 align:start position:0% forward and another round it's just kind 00:46:55.190 --> 00:46:57.539 align:start position:0% forward and another round it's just kind of<00:46:55.249> been<00:46:55.400> my<00:46:55.579> experience<00:46:55.759> that<00:46:56.480> if<00:46:56.720> we 00:46:57.539 --> 00:46:57.549 align:start position:0% of been my experience that if we 00:46:57.549 --> 00:47:00.789 align:start position:0% of been my experience that if we unanimously<00:46:58.549> vote<00:46:59.240> yes<00:46:59.539> we<00:47:00.170> never<00:47:00.380> hear<00:47:00.680> about 00:47:00.789 --> 00:47:00.799 align:start position:0% unanimously vote yes we never hear about 00:47:00.799 --> 00:47:04.930 align:start position:0% unanimously vote yes we never hear about this<00:47:01.039> issue<00:47:01.279> again<00:47:02.859> it<00:47:03.859> gets<00:47:04.009> lost<00:47:04.279> I<00:47:04.700> mean 00:47:04.930 --> 00:47:04.940 align:start position:0% this issue again it gets lost I mean 00:47:04.940 --> 00:47:06.910 align:start position:0% this issue again it gets lost I mean everybody's<00:47:05.630> busy<00:47:05.990> and<00:47:06.140> relays<00:47:06.380> a<00:47:06.410> lot<00:47:06.680> to<00:47:06.829> do 00:47:06.910 --> 00:47:06.920 align:start position:0% everybody's busy and relays a lot to do 00:47:06.920 --> 00:47:09.759 align:start position:0% everybody's busy and relays a lot to do it<00:47:07.039> just<00:47:07.160> gets<00:47:07.400> lost<00:47:07.809> if<00:47:08.809> it's<00:47:09.019> not<00:47:09.109> discussed 00:47:09.759 --> 00:47:09.769 align:start position:0% it just gets lost if it's not discussed 00:47:09.769 --> 00:47:13.450 align:start position:0% it just gets lost if it's not discussed at<00:47:09.980> council<00:47:10.430> so<00:47:11.089> my<00:47:11.779> inclination<00:47:12.109> is<00:47:12.769> not<00:47:13.160> to 00:47:13.450 --> 00:47:13.460 align:start position:0% at council so my inclination is not to 00:47:13.460 --> 00:47:15.489 align:start position:0% at council so my inclination is not to just<00:47:13.730> take<00:47:14.089> it<00:47:14.240> back<00:47:14.269> so<00:47:14.690> I<00:47:14.749> agree<00:47:15.319> with<00:47:15.380> you 00:47:15.489 --> 00:47:15.499 align:start position:0% just take it back so I agree with you 00:47:15.499 --> 00:47:17.380 align:start position:0% just take it back so I agree with you there<00:47:15.769> that<00:47:16.069> we<00:47:16.190> should<00:47:16.400> you<00:47:16.940> should<00:47:16.970> make<00:47:17.359> a 00:47:17.380 --> 00:47:17.390 align:start position:0% there that we should you should make a 00:47:17.390 --> 00:47:19.509 align:start position:0% there that we should you should make a decision<00:47:17.900> on<00:47:18.019> this<00:47:18.230> and<00:47:18.499> and<00:47:18.650> if<00:47:19.099> someone<00:47:19.400> were 00:47:19.509 --> 00:47:19.519 align:start position:0% decision on this and and if someone were 00:47:19.519 --> 00:47:22.440 align:start position:0% decision on this and and if someone were to<00:47:19.609> vote<00:47:19.759> against<00:47:20.299> it<00:47:20.420> and<00:47:20.710> you<00:47:21.710> know 00:47:22.440 --> 00:47:22.450 align:start position:0% to vote against it and you know 00:47:22.450 --> 00:47:24.640 align:start position:0% to vote against it and you know articulate<00:47:23.450> those<00:47:23.749> reasons<00:47:24.049> then<00:47:24.470> naturally 00:47:24.640 --> 00:47:24.650 align:start position:0% articulate those reasons then naturally 00:47:24.650 --> 00:47:26.920 align:start position:0% articulate those reasons then naturally that<00:47:25.069> would<00:47:25.700> go<00:47:25.880> before<00:47:26.210> council<00:47:26.599> then<00:47:26.749> that 00:47:26.920 --> 00:47:26.930 align:start position:0% that would go before council then that 00:47:26.930 --> 00:47:29.380 align:start position:0% that would go before council then that may<00:47:27.079> be<00:47:27.140> the<00:47:27.710> best<00:47:28.069> airing<00:47:28.489> we<00:47:28.640> could<00:47:29.150> get 00:47:29.380 --> 00:47:29.390 align:start position:0% may be the best airing we could get 00:47:29.390 --> 00:47:31.930 align:start position:0% may be the best airing we could get that's<00:47:29.779> what<00:47:29.960> I'm<00:47:30.049> thinking<00:47:30.470> on<00:47:30.680> and<00:47:31.279> it<00:47:31.880> could 00:47:31.930 --> 00:47:31.940 align:start position:0% that's what I'm thinking on and it could 00:47:31.940 --> 00:47:34.809 align:start position:0% that's what I'm thinking on and it could be<00:47:32.150> another<00:47:32.299> round<00:47:32.809> I<00:47:33.170> mean<00:47:33.410> my<00:47:33.950> my<00:47:34.369> thought 00:47:34.809 --> 00:47:34.819 align:start position:0% be another round I mean my my thought 00:47:34.819 --> 00:47:36.370 align:start position:0% be another round I mean my my thought would<00:47:35.029> be<00:47:35.059> that<00:47:35.420> they<00:47:35.569> would<00:47:35.749> discuss<00:47:36.170> it 00:47:36.370 --> 00:47:36.380 align:start position:0% would be that they would discuss it 00:47:36.380 --> 00:47:38.680 align:start position:0% would be that they would discuss it they'd<00:47:37.039> have<00:47:37.249> stay<00:47:37.640> with<00:47:37.819> our<00:47:37.970> staff<00:47:38.299> to<00:47:38.329> look 00:47:38.680 --> 00:47:38.690 align:start position:0% they'd have stay with our staff to look 00:47:38.690 --> 00:47:42.549 align:start position:0% they'd have stay with our staff to look at<00:47:38.900> it<00:47:39.079> and<00:47:39.230> it<00:47:39.859> might<00:47:40.130> be<00:47:40.279> in<00:47:40.430> round<00:47:41.380> 47<00:47:42.380> or 00:47:42.549 --> 00:47:42.559 align:start position:0% at it and it might be in round 47 or 00:47:42.559 --> 00:47:45.279 align:start position:0% at it and it might be in round 47 or whatever<00:47:42.650> comes<00:47:43.309> in<00:47:43.489> an<00:47:43.609> accident<00:47:44.029> and<00:47:44.359> then 00:47:45.279 --> 00:47:45.289 align:start position:0% whatever comes in an accident and then 00:47:45.289 --> 00:47:48.940 align:start position:0% whatever comes in an accident and then that<00:47:45.769> could<00:47:45.920> possibly<00:47:47.619> keep<00:47:48.619> us<00:47:48.799> from<00:47:48.890> having 00:47:48.940 --> 00:47:48.950 align:start position:0% that could possibly keep us from having 00:47:48.950 --> 00:47:50.859 align:start position:0% that could possibly keep us from having haven't<00:47:49.400> yet<00:47:49.579> another<00:47:49.789> public<00:47:50.210> hearing<00:47:50.239> on<00:47:50.630> a 00:47:50.859 --> 00:47:50.869 align:start position:0% haven't yet another public hearing on a 00:47:50.869 --> 00:47:52.690 align:start position:0% haven't yet another public hearing on a significant<00:47:51.440> change<00:47:51.769> yeah<00:47:52.160> I<00:47:52.279> like<00:47:52.430> to<00:47:52.519> say<00:47:52.609> in 00:47:52.690 --> 00:47:52.700 align:start position:0% significant change yeah I like to say in 00:47:52.700 --> 00:47:53.979 align:start position:0% significant change yeah I like to say in order<00:47:52.880> to<00:47:52.940> keep<00:47:53.089> the<00:47:53.150> ball<00:47:53.390> rolling<00:47:53.450> for<00:47:53.779> the 00:47:53.979 --> 00:47:53.989 align:start position:0% order to keep the ball rolling for the 00:47:53.989 --> 00:47:55.839 align:start position:0% order to keep the ball rolling for the good<00:47:54.170> parts<00:47:54.559> and<00:47:54.710> then<00:47:54.890> have<00:47:55.099> the<00:47:55.249> other<00:47:55.400> night 00:47:55.839 --> 00:47:55.849 align:start position:0% good parts and then have the other night 00:47:55.849 --> 00:47:59.920 align:start position:0% good parts and then have the other night exactly<00:47:57.880> so<00:47:58.880> i<00:47:58.910> will<00:47:59.239> take<00:47:59.390> the<00:47:59.569> hit<00:47:59.779> and 00:47:59.920 --> 00:47:59.930 align:start position:0% exactly so i will take the hit and 00:47:59.930 --> 00:48:01.749 align:start position:0% exactly so i will take the hit and voting<00:48:00.289> against<00:48:00.589> it<00:48:00.769> which<00:48:00.920> means<00:48:01.160> i<00:48:01.249> can't<00:48:01.489> we 00:48:01.749 --> 00:48:01.759 align:start position:0% voting against it which means i can't we 00:48:01.759 --> 00:48:03.460 align:start position:0% voting against it which means i can't we don't<00:48:01.910> have<00:48:01.999> anything<00:48:02.180> to<00:48:02.329> vote<00:48:02.599> on<00:48:02.630> yet<00:48:03.079> so 00:48:03.460 --> 00:48:03.470 align:start position:0% don't have anything to vote on yet so 00:48:03.470 --> 00:48:05.559 align:start position:0% don't have anything to vote on yet so we'll<00:48:03.829> have<00:48:03.980> to<00:48:04.190> and<00:48:04.789> by<00:48:05.059> the<00:48:05.089> way<00:48:05.239> thank<00:48:05.509> you 00:48:05.559 --> 00:48:05.569 align:start position:0% we'll have to and by the way thank you 00:48:05.569 --> 00:48:06.970 align:start position:0% we'll have to and by the way thank you all<00:48:05.779> for<00:48:05.989> making<00:48:06.079> what<00:48:06.410> i<00:48:06.440> thought<00:48:06.710> was<00:48:06.829> going 00:48:06.970 --> 00:48:06.980 align:start position:0% all for making what i thought was going 00:48:06.980 --> 00:48:09.279 align:start position:0% all for making what i thought was going to<00:48:07.039> be<00:48:07.130> a<00:48:07.190> really<00:48:07.549> easy<00:48:07.789> night<00:48:08.150> but<00:48:08.720> very 00:48:09.279 --> 00:48:09.289 align:start position:0% to be a really easy night but very 00:48:09.289 --> 00:48:13.870 align:start position:0% to be a really easy night but very complicated<00:48:11.499> issue<00:48:12.499> if<00:48:12.890> someone<00:48:13.279> would<00:48:13.549> would 00:48:13.870 --> 00:48:13.880 align:start position:0% complicated issue if someone would would 00:48:13.880 --> 00:48:15.640 align:start position:0% complicated issue if someone would would have<00:48:14.029> a<00:48:14.059> motion<00:48:14.359> in<00:48:14.630> mind<00:48:14.900> then<00:48:15.230> we<00:48:15.349> could<00:48:15.529> get 00:48:15.640 --> 00:48:15.650 align:start position:0% have a motion in mind then we could get 00:48:15.650 --> 00:48:17.140 align:start position:0% have a motion in mind then we could get that<00:48:15.710> out<00:48:16.009> there<00:48:16.190> we<00:48:16.400> could<00:48:16.549> Beit<00:48:16.849> it<00:48:16.999> a<00:48:17.029> little 00:48:17.140 --> 00:48:17.150 align:start position:0% that out there we could Beit it a little 00:48:17.150 --> 00:48:20.319 align:start position:0% that out there we could Beit it a little bit<00:48:17.329> and<00:48:17.569> and<00:48:18.170> take<00:48:18.739> it<00:48:18.890> from<00:48:19.009> there<00:48:19.180> only<00:48:20.180> on 00:48:20.319 --> 00:48:20.329 align:start position:0% bit and and take it from there only on 00:48:20.329 --> 00:48:24.640 align:start position:0% bit and and take it from there only on item<00:48:21.279> D<00:48:22.279> for<00:48:22.489> connectivity<00:48:22.970> at<00:48:23.239> this<00:48:23.359> point<00:48:23.650> so 00:48:24.640 --> 00:48:24.650 align:start position:0% item D for connectivity at this point so 00:48:24.650 --> 00:48:26.850 align:start position:0% item D for connectivity at this point so did<00:48:24.739> you<00:48:24.799> like<00:48:24.859> me<00:48:24.980> to<00:48:25.069> do<00:48:25.160> that 00:48:26.850 --> 00:48:26.860 align:start position:0% did you like me to do that 00:48:26.860 --> 00:48:30.360 align:start position:0% did you like me to do that I<00:48:28.140> motion<00:48:29.140> that<00:48:29.170> the<00:48:29.410> board<00:48:29.650> forward<00:48:30.040> ldo 00:48:30.360 --> 00:48:30.370 align:start position:0% I motion that the board forward ldo 00:48:30.370 --> 00:48:36.120 align:start position:0% I motion that the board forward ldo amendment<00:48:31.500> round<00:48:32.500> 31<00:48:33.010> item<00:48:33.370> a4<00:48:33.960> pl15<00:48:35.130> visit 00:48:36.120 --> 00:48:36.130 align:start position:0% amendment round 31 item a4 pl15 visit 00:48:36.130 --> 00:48:38.430 align:start position:0% amendment round 31 item a4 pl15 visit I'm<00:48:36.340> not<00:48:36.640> really<00:48:36.820> sure<00:48:36.970> how<00:48:37.300> to<00:48:37.330> word<00:48:37.660> this<00:48:37.900> ok 00:48:38.430 --> 00:48:38.440 align:start position:0% I'm not really sure how to word this ok 00:48:38.440 --> 00:48:40.140 align:start position:0% I'm not really sure how to word this ok we're<00:48:38.590> going<00:48:38.710> good<00:48:38.890> okay<00:48:39.190> to<00:48:39.850> the<00:48:39.970> town 00:48:40.140 --> 00:48:40.150 align:start position:0% we're going good okay to the town 00:48:40.150 --> 00:48:41.640 align:start position:0% we're going good okay to the town council<00:48:40.390> with<00:48:40.810> a<00:48:40.840> recommendation<00:48:41.200> for 00:48:41.640 --> 00:48:41.650 align:start position:0% council with a recommendation for 00:48:41.650 --> 00:48:44.040 align:start position:0% council with a recommendation for approval<00:48:42.040> that<00:48:42.580> is<00:48:42.870> consistent<00:48:43.870> with<00:48:43.900> the 00:48:44.040 --> 00:48:44.050 align:start position:0% approval that is consistent with the 00:48:44.050 --> 00:48:46.020 align:start position:0% approval that is consistent with the comprehensive<00:48:44.350> plan<00:48:44.650> and<00:48:45.010> all<00:48:45.130> other<00:48:45.340> plans 00:48:46.020 --> 00:48:46.030 align:start position:0% comprehensive plan and all other plans 00:48:46.030 --> 00:48:47.580 align:start position:0% comprehensive plan and all other plans and<00:48:46.330> is<00:48:46.480> reasonable<00:48:46.960> and<00:48:47.080> in<00:48:47.230> the<00:48:47.320> public 00:48:47.580 --> 00:48:47.590 align:start position:0% and is reasonable and in the public 00:48:47.590 --> 00:48:48.990 align:start position:0% and is reasonable and in the public interest<00:48:47.650> for<00:48:48.010> the<00:48:48.100> reasons<00:48:48.400> set<00:48:48.550> forth<00:48:48.610> in 00:48:48.990 --> 00:48:49.000 align:start position:0% interest for the reasons set forth in 00:48:49.000 --> 00:48:52.620 align:start position:0% interest for the reasons set forth in the<00:48:49.060> staff<00:48:49.360> report<00:48:49.600> or<00:48:49.990> presentation<00:48:51.600> have<00:48:52.600> a 00:48:52.620 --> 00:48:52.630 align:start position:0% the staff report or presentation have a 00:48:52.630 --> 00:48:56.220 align:start position:0% the staff report or presentation have a motion<00:48:52.870> to<00:48:53.140> approve<00:48:53.580> there<00:48:54.580> a<00:48:54.610> second<00:48:55.230> I'll 00:48:56.220 --> 00:48:56.230 align:start position:0% motion to approve there a second I'll 00:48:56.230 --> 00:49:01.290 align:start position:0% motion to approve there a second I'll second<00:48:57.030> now<00:48:58.030> discussion<00:48:58.720> I<00:49:00.030> like<00:49:01.030> the<00:49:01.210> idea 00:49:01.290 --> 00:49:01.300 align:start position:0% second now discussion I like the idea 00:49:01.300 --> 00:49:03.030 align:start position:0% second now discussion I like the idea that<00:49:01.480> we<00:49:01.720> are<00:49:01.870> trying<00:49:02.110> to<00:49:02.350> tear<00:49:02.590> it<00:49:02.740> and<00:49:02.830> take 00:49:03.030 --> 00:49:03.040 align:start position:0% that we are trying to tear it and take 00:49:03.040 --> 00:49:04.290 align:start position:0% that we are trying to tear it and take in<00:49:03.190> different<00:49:03.520> considerations<00:49:03.760> and 00:49:04.290 --> 00:49:04.300 align:start position:0% in different considerations and 00:49:04.300 --> 00:49:05.520 align:start position:0% in different considerations and conditions<00:49:04.720> and<00:49:04.960> that<00:49:05.050> we're<00:49:05.170> not<00:49:05.320> going<00:49:05.470> to 00:49:05.520 --> 00:49:05.530 align:start position:0% conditions and that we're not going to 00:49:05.530 --> 00:49:07.800 align:start position:0% conditions and that we're not going to hit<00:49:05.680> a<00:49:05.710> hundred<00:49:05.920> percent<00:49:06.070> of<00:49:06.340> everything<00:49:06.810> but 00:49:07.800 --> 00:49:07.810 align:start position:0% hit a hundred percent of everything but 00:49:07.810 --> 00:49:10.530 align:start position:0% hit a hundred percent of everything but I<00:49:07.870> also<00:49:08.160> like<00:49:09.160> the<00:49:09.340> fact<00:49:09.370> that<00:49:09.610> this<00:49:10.120> is<00:49:10.330> still 00:49:10.530 --> 00:49:10.540 align:start position:0% I also like the fact that this is still 00:49:10.540 --> 00:49:12.180 align:start position:0% I also like the fact that this is still open<00:49:10.660> for<00:49:10.810> further<00:49:11.080> discussion<00:49:11.350> as<00:49:11.860> we 00:49:12.180 --> 00:49:12.190 align:start position:0% open for further discussion as we 00:49:12.190 --> 00:49:18.480 align:start position:0% open for further discussion as we discussed<00:49:12.730> in<00:49:13.090> our<00:49:13.630> game<00:49:14.020> plan<00:49:17.280> anything<00:49:18.280> to 00:49:18.480 --> 00:49:18.490 align:start position:0% discussed in our game plan anything to 00:49:18.490 --> 00:49:22.430 align:start position:0% discussed in our game plan anything to add<00:49:18.580> I<00:49:18.880> don't<00:49:19.450> have<00:49:19.510> anything<00:49:19.720> about<00:49:20.200> that<00:49:20.290> no 00:49:22.430 --> 00:49:22.440 align:start position:0% add I don't have anything about that no 00:49:22.440 --> 00:49:25.290 align:start position:0% add I don't have anything about that no would<00:49:23.440> you<00:49:23.530> like<00:49:23.560> to<00:49:23.860> yes<00:49:24.550> make<00:49:24.970> a<00:49:25.000> statement 00:49:25.290 --> 00:49:25.300 align:start position:0% would you like to yes make a statement 00:49:25.300 --> 00:49:28.140 align:start position:0% would you like to yes make a statement okay<00:49:25.780> so<00:49:26.100> you<00:49:27.100> know<00:49:27.250> I<00:49:27.280> pretty<00:49:27.730> much<00:49:27.820> already 00:49:28.140 --> 00:49:28.150 align:start position:0% okay so you know I pretty much already 00:49:28.150 --> 00:49:30.210 align:start position:0% okay so you know I pretty much already said<00:49:28.540> this<00:49:28.750> but<00:49:28.810> for<00:49:29.320> the<00:49:29.440> record<00:49:29.620> I'm<00:49:30.040> going 00:49:30.210 --> 00:49:30.220 align:start position:0% said this but for the record I'm going 00:49:30.220 --> 00:49:34.110 align:start position:0% said this but for the record I'm going to<00:49:30.340> vote<00:49:30.430> against<00:49:30.880> this<00:49:31.060> I<00:49:31.360> think<00:49:33.060> this<00:49:34.060> is 00:49:34.110 --> 00:49:34.120 align:start position:0% to vote against this I think this is 00:49:34.120 --> 00:49:36.780 align:start position:0% to vote against this I think this is good<00:49:34.480> I<00:49:34.750> like<00:49:35.290> it<00:49:35.560> I<00:49:35.710> like<00:49:35.770> everything<00:49:36.220> in<00:49:36.610> it 00:49:36.780 --> 00:49:36.790 align:start position:0% good I like it I like everything in it 00:49:36.790 --> 00:49:40.670 align:start position:0% good I like it I like everything in it but<00:49:37.120> I<00:49:37.180> feel<00:49:37.540> like<00:49:38.220> it<00:49:39.220> should<00:49:39.520> be<00:49:39.550> expanded 00:49:40.670 --> 00:49:40.680 align:start position:0% but I feel like it should be expanded 00:49:40.680 --> 00:49:44.820 align:start position:0% but I feel like it should be expanded with<00:49:41.680> one<00:49:42.640> more<00:49:42.910> provision<00:49:43.840> which<00:49:44.260> protects 00:49:44.820 --> 00:49:44.830 align:start position:0% with one more provision which protects 00:49:44.830 --> 00:49:48.150 align:start position:0% with one more provision which protects tier<00:49:45.310> 1<00:49:45.730> 2<00:49:46.150> and<00:49:46.420> 3<00:49:46.510> tier<00:49:47.290> 2<00:49:47.410> and<00:49:47.500> 3<00:49:47.680> are<00:49:47.710> already 00:49:48.150 --> 00:49:48.160 align:start position:0% tier 1 2 and 3 tier 2 and 3 are already 00:49:48.160 --> 00:49:50.850 align:start position:0% tier 1 2 and 3 tier 2 and 3 are already basically<00:49:48.460> protected<00:49:49.270> but<00:49:49.750> also<00:49:49.960> for<00:49:50.320> textear 00:49:50.850 --> 00:49:50.860 align:start position:0% basically protected but also for textear 00:49:50.860 --> 00:49:53.520 align:start position:0% basically protected but also for textear one<00:49:51.130> from<00:49:52.030> adjacent<00:49:52.390> developed<00:49:53.170> non 00:49:53.520 --> 00:49:53.530 align:start position:0% one from adjacent developed non 00:49:53.530 --> 00:49:57.410 align:start position:0% one from adjacent developed non residential<00:49:54.330> development<00:49:55.330> either<00:49:56.020> MXD<00:49:56.800> or 00:49:57.410 --> 00:49:57.420 align:start position:0% residential development either MXD or 00:49:57.420 --> 00:50:00.060 align:start position:0% residential development either MXD or commercial<00:49:58.420> or<00:49:58.510> office<00:49:58.930> or<00:49:59.110> whatever<00:49:59.800> it<00:49:59.980> is 00:50:00.060 --> 00:50:00.070 align:start position:0% commercial or office or whatever it is 00:50:00.070 --> 00:50:03.360 align:start position:0% commercial or office or whatever it is if<00:50:00.340> it's<00:50:00.520> not<00:50:00.700> a<00:50:00.730> traditional<00:50:02.370> neighborhood 00:50:03.360 --> 00:50:03.370 align:start position:0% if it's not a traditional neighborhood 00:50:03.370 --> 00:50:06.900 align:start position:0% if it's not a traditional neighborhood and<00:50:04.060> then<00:50:04.240> they<00:50:04.540> need<00:50:04.750> some<00:50:05.020> protection<00:50:05.910> in 00:50:06.900 --> 00:50:06.910 align:start position:0% and then they need some protection in 00:50:06.910 --> 00:50:10.740 align:start position:0% and then they need some protection in the<00:50:06.970> form<00:50:07.420> of<00:50:07.960> being<00:50:08.410> able<00:50:08.620> to<00:50:08.800> look<00:50:09.790> at<00:50:10.060> zoning 00:50:10.740 --> 00:50:10.750 align:start position:0% the form of being able to look at zoning 00:50:10.750 --> 00:50:17.270 align:start position:0% the form of being able to look at zoning conditions<00:50:13.290> versus<00:50:14.290> waiting<00:50:14.620> for<00:50:14.800> site<00:50:14.980> plan 00:50:17.270 --> 00:50:17.280 align:start position:0% 00:50:17.280 --> 00:50:20.280 align:start position:0% any<00:50:18.280> further<00:50:18.430> discussion<00:50:18.930> yes<00:50:19.930> i'm<00:50:20.110> also 00:50:20.280 --> 00:50:20.290 align:start position:0% any further discussion yes i'm also 00:50:20.290 --> 00:50:22.140 align:start position:0% any further discussion yes i'm also going<00:50:20.620> to<00:50:20.710> income<00:50:21.280> on<00:50:21.400> board<00:50:21.580> with<00:50:21.670> Carla<00:50:21.970> here 00:50:22.140 --> 00:50:22.150 align:start position:0% going to income on board with Carla here 00:50:22.150 --> 00:50:26.160 align:start position:0% going to income on board with Carla here and<00:50:22.980> opposing<00:50:23.980> this<00:50:24.130> I<00:50:24.850> think<00:50:25.360> on<00:50:25.660> paper<00:50:25.990> is 00:50:26.160 --> 00:50:26.170 align:start position:0% and opposing this I think on paper is 00:50:26.170 --> 00:50:29.760 align:start position:0% and opposing this I think on paper is really<00:50:26.470> good<00:50:27.210> to<00:50:28.210> be<00:50:28.300> honest<00:50:28.630> I<00:50:28.780> kind<00:50:29.530> of<00:50:29.620> came 00:50:29.760 --> 00:50:29.770 align:start position:0% really good to be honest I kind of came 00:50:29.770 --> 00:50:31.980 align:start position:0% really good to be honest I kind of came in<00:50:29.890> here<00:50:30.070> I<00:50:30.340> wanted<00:50:30.850> to<00:50:30.940> support<00:50:31.120> this<00:50:31.420> but<00:50:31.720> in 00:50:31.980 --> 00:50:31.990 align:start position:0% in here I wanted to support this but in 00:50:31.990 --> 00:50:34.020 align:start position:0% in here I wanted to support this but in some<00:50:32.320> of<00:50:32.440> the<00:50:32.530> discussion<00:50:33.070> specifically<00:50:33.910> with 00:50:34.020 --> 00:50:34.030 align:start position:0% some of the discussion specifically with 00:50:34.030 --> 00:50:36.390 align:start position:0% some of the discussion specifically with you<00:50:34.060> residential<00:50:34.720> and<00:50:34.870> the<00:50:34.930> other<00:50:35.080> uses<00:50:35.410> you 00:50:36.390 --> 00:50:36.400 align:start position:0% you residential and the other uses you 00:50:36.400 --> 00:50:37.200 align:start position:0% you residential and the other uses you know<00:50:36.490> I<00:50:36.520> think<00:50:36.700> that<00:50:36.790> something<00:50:37.000> that<00:50:37.090> really 00:50:37.200 --> 00:50:37.210 align:start position:0% know I think that something that really 00:50:37.210 --> 00:50:38.490 align:start position:0% know I think that something that really should<00:50:37.420> be<00:50:37.450> taken<00:50:37.720> into<00:50:37.810> account<00:50:37.900> here<00:50:38.350> I 00:50:38.490 --> 00:50:38.500 align:start position:0% should be taken into account here I 00:50:38.500 --> 00:50:39.569 align:start position:0% should be taken into account here I think<00:50:39.400> this 00:50:39.569 --> 00:50:39.579 align:start position:0% think this 00:50:39.579 --> 00:50:41.670 align:start position:0% think this is<00:50:39.640> really<00:50:40.059> a<00:50:40.299> better<00:50:40.900> step<00:50:41.289> I<00:50:41.440> definitely 00:50:41.670 --> 00:50:41.680 align:start position:0% is really a better step I definitely 00:50:41.680 --> 00:50:42.479 align:start position:0% is really a better step I definitely think<00:50:41.829> we're<00:50:41.979> going<00:50:42.099> in<00:50:42.190> the<00:50:42.279> right<00:50:42.309> direction 00:50:42.479 --> 00:50:42.489 align:start position:0% think we're going in the right direction 00:50:42.489 --> 00:50:43.890 align:start position:0% think we're going in the right direction but<00:50:42.819> I<00:50:43.029> just<00:50:43.239> think<00:50:43.390> that's<00:50:43.479> something<00:50:43.719> that 00:50:43.890 --> 00:50:43.900 align:start position:0% but I just think that's something that 00:50:43.900 --> 00:50:46.019 align:start position:0% but I just think that's something that that<00:50:44.650> council<00:50:45.009> definitely<00:50:45.459> is<00:50:45.519> keep<00:50:45.700> in<00:50:45.819> mind 00:50:46.019 --> 00:50:46.029 align:start position:0% that council definitely is keep in mind 00:50:46.029 --> 00:50:47.670 align:start position:0% that council definitely is keep in mind and<00:50:46.299> maybe<00:50:46.630> we<00:50:46.809> can<00:50:46.900> come<00:50:47.049> back<00:50:47.200> with<00:50:47.469> with 00:50:47.670 --> 00:50:47.680 align:start position:0% and maybe we can come back with with 00:50:47.680 --> 00:50:49.739 align:start position:0% and maybe we can come back with with another<00:50:47.950> round<00:50:48.190> and<00:50:48.400> address<00:50:49.029> that<00:50:49.239> specific 00:50:49.739 --> 00:50:49.749 align:start position:0% another round and address that specific 00:50:49.749 --> 00:50:52.229 align:start position:0% another round and address that specific issue<00:50:50.140> along<00:50:50.950> with<00:50:51.190> everything<00:50:51.670> else<00:50:51.880> which 00:50:52.229 --> 00:50:52.239 align:start position:0% issue along with everything else which 00:50:52.239 --> 00:50:56.160 align:start position:0% issue along with everything else which again<00:50:52.450> I<00:50:52.569> think<00:50:52.630> is<00:50:52.839> pretty<00:50:53.079> solid<00:50:55.019> thank<00:50:56.019> you 00:50:56.160 --> 00:50:56.170 align:start position:0% again I think is pretty solid thank you 00:50:56.170 --> 00:50:58.739 align:start position:0% again I think is pretty solid thank you any<00:50:56.469> other<00:50:56.680> comments<00:50:57.670> before<00:50:57.999> we<00:50:58.150> meeting<00:50:58.630> in 00:50:58.739 --> 00:50:58.749 align:start position:0% any other comments before we meeting in 00:50:58.749 --> 00:51:03.390 align:start position:0% any other comments before we meeting in the<00:50:58.869> same<00:50:59.109> direction<00:50:59.259> i'm<00:50:59.739> afraid<00:51:00.099> that<00:51:02.400> makes 00:51:03.390 --> 00:51:03.400 align:start position:0% the same direction i'm afraid that makes 00:51:03.400 --> 00:51:06.319 align:start position:0% the same direction i'm afraid that makes three<00:51:03.779> you<00:51:04.779> like<00:51:04.930> to<00:51:05.109> explain<00:51:05.319> it<00:51:05.589> further 00:51:06.319 --> 00:51:06.329 align:start position:0% three you like to explain it further 00:51:06.329 --> 00:51:10.650 align:start position:0% three you like to explain it further well<00:51:07.329> i<00:51:07.359> wasn't<00:51:07.809> in<00:51:08.079> on<00:51:08.259> the<00:51:08.849> work<00:51:09.849> session<00:51:10.150> so 00:51:10.650 --> 00:51:10.660 align:start position:0% well i wasn't in on the work session so 00:51:10.660 --> 00:51:12.839 align:start position:0% well i wasn't in on the work session so in<00:51:11.079> some<00:51:11.440> ways<00:51:11.469> there<00:51:12.099> are<00:51:12.130> some<00:51:12.549> small<00:51:12.819> things 00:51:12.839 --> 00:51:12.849 align:start position:0% in some ways there are some small things 00:51:12.849 --> 00:51:15.359 align:start position:0% in some ways there are some small things about<00:51:13.420> this<00:51:13.660> that<00:51:13.719> i'd<00:51:14.049> like<00:51:14.289> to<00:51:14.440> have<00:51:14.619> cast 00:51:15.359 --> 00:51:15.369 align:start position:0% about this that i'd like to have cast 00:51:15.369 --> 00:51:17.729 align:start position:0% about this that i'd like to have cast but<00:51:16.299> i<00:51:16.359> really<00:51:16.630> didn't<00:51:16.900> think<00:51:16.930> about<00:51:17.200> until<00:51:17.529> i 00:51:17.729 --> 00:51:17.739 align:start position:0% but i really didn't think about until i 00:51:17.739 --> 00:51:19.289 align:start position:0% but i really didn't think about until i started<00:51:18.249> reading<00:51:18.489> the<00:51:18.729> whole<00:51:18.849> thing<00:51:19.119> over 00:51:19.289 --> 00:51:19.299 align:start position:0% started reading the whole thing over 00:51:19.299 --> 00:51:22.739 align:start position:0% started reading the whole thing over again<00:51:19.739> but<00:51:20.739> i<00:51:20.769> do<00:51:20.920> believe<00:51:21.160> that<00:51:21.579> we've<00:51:22.420> had<00:51:22.569> at 00:51:22.739 --> 00:51:22.749 align:start position:0% again but i do believe that we've had at 00:51:22.749 --> 00:51:24.630 align:start position:0% again but i do believe that we've had at least<00:51:22.900> one<00:51:23.229> case<00:51:23.529> where<00:51:23.589> there<00:51:24.489> was<00:51:24.609> a 00:51:24.630 --> 00:51:24.640 align:start position:0% least one case where there was a 00:51:24.640 --> 00:51:27.199 align:start position:0% least one case where there was a neighborhood<00:51:25.329> going<00:51:25.719> in<00:51:25.959> adjacent<00:51:26.469> to<00:51:26.979> a 00:51:27.199 --> 00:51:27.209 align:start position:0% neighborhood going in adjacent to a 00:51:27.209 --> 00:51:30.630 align:start position:0% neighborhood going in adjacent to a commercial<00:51:28.209> development<00:51:29.140> and<00:51:29.519> there<00:51:30.519> was<00:51:30.609> a 00:51:30.630 --> 00:51:30.640 align:start position:0% commercial development and there was a 00:51:30.640 --> 00:51:32.729 align:start position:0% commercial development and there was a big<00:51:30.849> issue<00:51:31.089> with<00:51:31.209> connectivity<00:51:31.900> on<00:51:32.289> that<00:51:32.529> one 00:51:32.729 --> 00:51:32.739 align:start position:0% big issue with connectivity on that one 00:51:32.739 --> 00:51:35.489 align:start position:0% big issue with connectivity on that one and<00:51:33.299> so<00:51:34.299> I<00:51:34.329> do<00:51:34.479> think<00:51:34.900> this<00:51:35.019> is<00:51:35.259> something 00:51:35.489 --> 00:51:35.499 align:start position:0% and so I do think this is something 00:51:35.499 --> 00:51:38.009 align:start position:0% and so I do think this is something that's<00:51:35.769> worthwhile<00:51:36.069> to<00:51:36.759> be<00:51:36.910> laid<00:51:37.329> out<00:51:37.359> should 00:51:38.009 --> 00:51:38.019 align:start position:0% that's worthwhile to be laid out should 00:51:38.019 --> 00:51:40.739 align:start position:0% that's worthwhile to be laid out should be<00:51:38.170> laid<00:51:38.380> out<00:51:38.969> probably<00:51:39.969> should<00:51:40.450> not<00:51:40.630> have 00:51:40.739 --> 00:51:40.749 align:start position:0% be laid out probably should not have 00:51:40.749 --> 00:51:43.079 align:start position:0% be laid out probably should not have been<00:51:40.930> forgotten<00:51:41.289> but<00:51:41.709> I<00:51:41.769> don't<00:51:42.579> know<00:51:42.789> why<00:51:43.029> it 00:51:43.079 --> 00:51:43.089 align:start position:0% been forgotten but I don't know why it 00:51:43.089 --> 00:51:50.339 align:start position:0% been forgotten but I don't know why it wasn't<00:51:43.499> so<00:51:45.059> I'm<00:51:46.059> in<00:51:46.690> Carlos<00:51:47.140> camp<00:51:47.410> on<00:51:49.349> anyone 00:51:50.339 --> 00:51:50.349 align:start position:0% wasn't so I'm in Carlos camp on anyone 00:51:50.349 --> 00:51:54.029 align:start position:0% wasn't so I'm in Carlos camp on anyone else<00:51:51.989> hopefully<00:51:52.989> this<00:51:53.109> is<00:51:53.229> not<00:51:53.410> out<00:51:53.709> of<00:51:53.739> order 00:51:54.029 --> 00:51:54.039 align:start position:0% else hopefully this is not out of order 00:51:54.039 --> 00:51:55.410 align:start position:0% else hopefully this is not out of order but<00:51:54.130> I<00:51:54.190> have<00:51:54.279> a<00:51:54.339> question<00:51:54.549> on<00:51:54.880> this<00:51:55.059> if<00:51:55.239> this 00:51:55.410 --> 00:51:55.420 align:start position:0% but I have a question on this if this 00:51:55.420 --> 00:51:57.209 align:start position:0% but I have a question on this if this would<00:51:55.719> be<00:51:55.930> voted<00:51:56.380> down<00:51:56.410> being<00:51:56.829> an<00:51:56.920> Lda 00:51:57.209 --> 00:51:57.219 align:start position:0% would be voted down being an Lda 00:51:57.219 --> 00:52:00.359 align:start position:0% would be voted down being an Lda amendment<00:51:57.819> what<00:51:58.209> is<00:51:58.390> the<00:51:58.569> next<00:51:58.779> step<00:51:59.140> for<00:51:59.619> this 00:52:00.359 --> 00:52:00.369 align:start position:0% amendment what is the next step for this 00:52:00.369 --> 00:52:02.880 align:start position:0% amendment what is the next step for this does<00:52:00.759> it<00:52:00.910> come<00:52:01.089> right<00:52:01.299> back<00:52:01.509> to<00:52:01.719> us<00:52:01.869> with<00:52:02.229> it 00:52:02.880 --> 00:52:02.890 align:start position:0% does it come right back to us with it 00:52:02.890 --> 00:52:05.430 align:start position:0% does it come right back to us with it would<00:52:03.130> it<00:52:03.699> would<00:52:03.729> still<00:52:04.180> move<00:52:04.630> forward<00:52:04.660> to 00:52:05.430 --> 00:52:05.440 align:start position:0% would it would still move forward to 00:52:05.440 --> 00:52:09.930 align:start position:0% would it would still move forward to counsel<00:52:06.339> for<00:52:06.670> a<00:52:06.729> decision<00:52:07.170> and<00:52:08.170> then<00:52:08.699> as<00:52:09.699> in 00:52:09.930 --> 00:52:09.940 align:start position:0% counsel for a decision and then as in 00:52:09.940 --> 00:52:11.789 align:start position:0% counsel for a decision and then as in the<00:52:10.150> boat<00:52:10.329> council<00:52:10.839> takes<00:52:11.109> your<00:52:11.349> vote<00:52:11.529> into 00:52:11.789 --> 00:52:11.799 align:start position:0% the boat council takes your vote into 00:52:11.799 --> 00:52:13.680 align:start position:0% the boat council takes your vote into consideration<00:52:12.519> and<00:52:12.699> then<00:52:12.819> they<00:52:12.999> will<00:52:13.269> make 00:52:13.680 --> 00:52:13.690 align:start position:0% consideration and then they will make 00:52:13.690 --> 00:52:16.650 align:start position:0% consideration and then they will make their<00:52:13.869> decision<00:52:14.349> which<00:52:14.559> could<00:52:14.829> be<00:52:15.089> to<00:52:16.089> make 00:52:16.650 --> 00:52:16.660 align:start position:0% their decision which could be to make 00:52:16.660 --> 00:52:20.009 align:start position:0% their decision which could be to make changes<00:52:16.959> or<00:52:17.259> send<00:52:17.709> it<00:52:17.829> back<00:52:18.549> or<00:52:18.940> vote<00:52:19.630> on<00:52:19.809> it 00:52:20.009 --> 00:52:20.019 align:start position:0% changes or send it back or vote on it 00:52:20.019 --> 00:52:22.349 align:start position:0% changes or send it back or vote on it with<00:52:20.170> some<00:52:20.410> changes<00:52:20.890> but<00:52:21.099> that<00:52:21.969> would<00:52:22.119> be<00:52:22.150> up 00:52:22.349 --> 00:52:22.359 align:start position:0% with some changes but that would be up 00:52:22.359 --> 00:52:25.469 align:start position:0% with some changes but that would be up to<00:52:22.390> counsel<00:52:22.959> thank<00:52:23.319> you<00:52:24.119> does<00:52:25.119> anyone<00:52:25.329> else 00:52:25.469 --> 00:52:25.479 align:start position:0% to counsel thank you does anyone else 00:52:25.479 --> 00:52:28.439 align:start position:0% to counsel thank you does anyone else have<00:52:25.660> any<00:52:25.809> other<00:52:26.849> comments<00:52:27.849> for<00:52:27.910> discussion 00:52:28.439 --> 00:52:28.449 align:start position:0% have any other comments for discussion 00:52:28.449 --> 00:52:31.319 align:start position:0% have any other comments for discussion if<00:52:29.259> not<00:52:29.920> then<00:52:30.249> we'll<00:52:30.279> have<00:52:30.640> to<00:52:30.789> do<00:52:30.910> a<00:52:30.940> show<00:52:31.209> of 00:52:31.319 --> 00:52:31.329 align:start position:0% if not then we'll have to do a show of 00:52:31.329 --> 00:52:32.640 align:start position:0% if not then we'll have to do a show of hands<00:52:31.569> here<00:52:31.779> because<00:52:32.079> I<00:52:32.259> think<00:52:32.319> we're<00:52:32.559> going 00:52:32.640 --> 00:52:32.650 align:start position:0% hands here because I think we're going 00:52:32.650 --> 00:52:35.069 align:start position:0% hands here because I think we're going to<00:52:32.739> have<00:52:32.829> a<00:52:32.890> a<00:52:33.190> very<00:52:33.880> close<00:52:34.359> vote<00:52:34.390> all<00:52:34.869> those<00:52:34.900> in 00:52:35.069 --> 00:52:35.079 align:start position:0% to have a a very close vote all those in 00:52:35.079 --> 00:52:38.519 align:start position:0% to have a a very close vote all those in favor<00:52:35.619> of<00:52:35.799> adopting<00:52:36.130> this<00:52:36.670> L<00:52:37.509> do<00:52:37.809> as<00:52:38.170> the 00:52:38.519 --> 00:52:38.529 align:start position:0% favor of adopting this L do as the 00:52:38.529 --> 00:52:40.829 align:start position:0% favor of adopting this L do as the motion<00:52:38.920> stated<00:52:39.309> please<00:52:40.029> raise<00:52:40.449> your<00:52:40.479> hand<00:52:40.749> and 00:52:40.829 --> 00:52:40.839 align:start position:0% motion stated please raise your hand and 00:52:40.839 --> 00:52:44.579 align:start position:0% motion stated please raise your hand and say<00:52:41.190> hi<00:52:42.509> all<00:52:43.509> those<00:52:43.690> opposed<00:52:44.049> raise<00:52:44.289> your<00:52:44.440> hand 00:52:44.579 --> 00:52:44.589 align:start position:0% say hi all those opposed raise your hand 00:52:44.589 --> 00:52:47.009 align:start position:0% say hi all those opposed raise your hand and<00:52:44.619> say<00:52:44.739> no<00:52:44.949> if<00:52:45.069> you<00:52:45.190> please<00:52:45.430> we<00:52:46.269> have<00:52:46.359> a<00:52:46.390> 4-3 00:52:47.009 --> 00:52:47.019 align:start position:0% and say no if you please we have a 4-3 00:52:47.019 --> 00:52:56.150 align:start position:0% and say no if you please we have a 4-3 vote<00:52:47.170> in<00:52:47.349> favor<00:52:48.779> really<00:52:49.779> weak 00:52:56.150 --> 00:52:56.160 align:start position:0% 00:52:56.160 --> 00:53:07.499 align:start position:0% now<00:52:57.160> we're<00:52:57.369> taking<00:52:57.729> up<00:52:57.849> the<00:52:58.119> second<00:52:58.539> item<00:53:06.509> does 00:53:07.499 --> 00:53:07.509 align:start position:0% now we're taking up the second item does 00:53:07.509 --> 00:53:08.940 align:start position:0% now we're taking up the second item does anyone<00:53:07.749> have<00:53:08.019> any<00:53:08.170> questions<00:53:08.259> for<00:53:08.799> miss 00:53:08.940 --> 00:53:08.950 align:start position:0% anyone have any questions for miss 00:53:08.950 --> 00:53:13.319 align:start position:0% anyone have any questions for miss Biermann<00:53:09.869> on<00:53:10.869> item<00:53:11.289> to<00:53:11.940> low<00:53:12.940> density 00:53:13.319 --> 00:53:13.329 align:start position:0% Biermann on item to low density 00:53:13.329 --> 00:53:15.839 align:start position:0% Biermann on item to low density residential<00:53:13.809> standards<00:53:14.380> can<00:53:15.309> you<00:53:15.400> go<00:53:15.519> back<00:53:15.670> to 00:53:15.839 --> 00:53:15.849 align:start position:0% residential standards can you go back to 00:53:15.849 --> 00:53:18.930 align:start position:0% residential standards can you go back to that<00:53:15.940> nifty<00:53:16.210> gifty<00:53:16.660> chart<00:53:16.869> also<00:53:17.400> with<00:53:18.400> the<00:53:18.519> r12 00:53:18.930 --> 00:53:18.940 align:start position:0% that nifty gifty chart also with the r12 00:53:18.940 --> 00:53:26.039 align:start position:0% that nifty gifty chart also with the r12 they<00:53:19.119> are<00:53:19.269> 8<00:53:19.450> and<00:53:21.450> that<00:53:22.450> one<00:53:22.690> thank<00:53:22.930> you<00:53:25.049> why 00:53:26.039 --> 00:53:26.049 align:start position:0% they are 8 and that one thank you why 00:53:26.049 --> 00:53:28.410 align:start position:0% they are 8 and that one thank you why are<00:53:26.109> we<00:53:26.259> including<00:53:26.380> are<00:53:26.890> 8<00:53:27.130> and<00:53:27.369> very<00:53:28.180> low 00:53:28.410 --> 00:53:28.420 align:start position:0% are we including are 8 and very low 00:53:28.420 --> 00:53:35.459 align:start position:0% are we including are 8 and very low density<00:53:29.099> I'm<00:53:30.099> just<00:53:30.279> curious<00:53:32.369> when<00:53:33.369> we<00:53:33.839> as<00:53:34.839> part 00:53:35.459 --> 00:53:35.469 align:start position:0% density I'm just curious when we as part 00:53:35.469 --> 00:53:38.279 align:start position:0% density I'm just curious when we as part of<00:53:35.619> the<00:53:35.739> history<00:53:35.920> of<00:53:36.190> this<00:53:36.430> when<00:53:36.789> we<00:53:37.029> as<00:53:37.779> this 00:53:38.279 --> 00:53:38.289 align:start position:0% of the history of this when we as this 00:53:38.289 --> 00:53:40.559 align:start position:0% of the history of this when we as this has<00:53:38.529> gone<00:53:38.739> through<00:53:39.160> the<00:53:39.430> various<00:53:39.910> council 00:53:40.559 --> 00:53:40.569 align:start position:0% has gone through the various council 00:53:40.569 --> 00:53:42.420 align:start position:0% has gone through the various council work<00:53:40.719> sessions<00:53:41.229> and<00:53:41.349> getting<00:53:41.619> feedback<00:53:41.829> on 00:53:42.420 --> 00:53:42.430 align:start position:0% work sessions and getting feedback on 00:53:42.430 --> 00:53:45.420 align:start position:0% work sessions and getting feedback on council<00:53:43.420> with<00:53:43.539> what<00:53:44.039> through<00:53:45.039> the<00:53:45.190> work 00:53:45.420 --> 00:53:45.430 align:start position:0% council with what through the work 00:53:45.430 --> 00:53:50.849 align:start position:0% council with what through the work session<00:53:45.700> process<00:53:46.239> when<00:53:47.140> we<00:53:48.359> first<00:53:49.619> the<00:53:50.619> first 00:53:50.849 --> 00:53:50.859 align:start position:0% session process when we first the first 00:53:50.859 --> 00:53:52.769 align:start position:0% session process when we first the first public<00:53:51.460> hearing<00:53:51.849> that<00:53:52.029> we<00:53:52.150> had<00:53:52.359> the<00:53:52.539> first 00:53:52.769 --> 00:53:52.779 align:start position:0% public hearing that we had the first 00:53:52.779 --> 00:53:57.769 align:start position:0% public hearing that we had the first draft<00:53:53.079> that<00:53:53.380> we<00:53:53.529> had<00:53:53.799> we<00:53:54.690> had<00:53:55.690> included<00:53:56.410> some 00:53:57.769 --> 00:53:57.779 align:start position:0% draft that we had we had included some 00:53:57.779 --> 00:54:00.390 align:start position:0% draft that we had we had included some the<00:53:58.779> approach<00:53:59.140> was<00:53:59.349> a<00:53:59.410> little<00:53:59.739> bit<00:53:59.859> different 00:54:00.390 --> 00:54:00.400 align:start position:0% the approach was a little bit different 00:54:00.400 --> 00:54:06.420 align:start position:0% the approach was a little bit different and<00:54:00.839> we<00:54:01.839> actually<00:54:02.079> put<00:54:02.650> into<00:54:03.069> the<00:54:05.430> dimensional 00:54:06.420 --> 00:54:06.430 align:start position:0% and we actually put into the dimensional 00:54:06.430 --> 00:54:11.700 align:start position:0% and we actually put into the dimensional standards<00:54:07.029> that<00:54:09.089> applied<00:54:10.089> within<00:54:10.989> different 00:54:11.700 --> 00:54:11.710 align:start position:0% standards that applied within different 00:54:11.710 --> 00:54:14.039 align:start position:0% standards that applied within different districts<00:54:12.460> for<00:54:12.579> single-family<00:54:13.059> development 00:54:14.039 --> 00:54:14.049 align:start position:0% districts for single-family development 00:54:14.049 --> 00:54:18.920 align:start position:0% districts for single-family development that<00:54:14.799> if<00:54:15.219> you're<00:54:15.700> in<00:54:15.969> an<00:54:16.150> ldr<00:54:16.809> area<00:54:17.200> you<00:54:17.499> had<00:54:17.910> a 00:54:18.920 --> 00:54:18.930 align:start position:0% that if you're in an ldr area you had a 00:54:18.930 --> 00:54:21.479 align:start position:0% that if you're in an ldr area you had a minimum<00:54:19.930> even<00:54:20.319> if<00:54:20.440> it<00:54:20.559> was<00:54:20.710> TR<00:54:21.099> you<00:54:21.279> had<00:54:21.460> a 00:54:21.479 --> 00:54:21.489 align:start position:0% minimum even if it was TR you had a 00:54:21.489 --> 00:54:23.819 align:start position:0% minimum even if it was TR you had a minimum<00:54:21.789> lot<00:54:21.969> size<00:54:22.029> that<00:54:22.900> matched<00:54:23.319> up<00:54:23.650> with 00:54:23.819 --> 00:54:23.829 align:start position:0% minimum lot size that matched up with 00:54:23.829 --> 00:54:26.089 align:start position:0% minimum lot size that matched up with what<00:54:24.039> was<00:54:24.190> our<00:54:24.339> 12<00:54:24.670> and<00:54:24.940> that<00:54:25.569> was<00:54:25.779> basically 00:54:26.089 --> 00:54:26.099 align:start position:0% what was our 12 and that was basically 00:54:26.099 --> 00:54:31.140 align:start position:0% what was our 12 and that was basically consistent<00:54:27.099> with<00:54:27.609> the<00:54:27.819> VL<00:54:28.269> our<00:54:28.989> areas<00:54:29.410> to<00:54:30.150> when 00:54:31.140 --> 00:54:31.150 align:start position:0% consistent with the VL our areas to when 00:54:31.150 --> 00:54:33.630 align:start position:0% consistent with the VL our areas to when we<00:54:31.329> took<00:54:31.630> that<00:54:32.019> to<00:54:32.920> the<00:54:32.950> initial<00:54:33.369> public 00:54:33.630 --> 00:54:33.640 align:start position:0% we took that to the initial public 00:54:33.640 --> 00:54:37.170 align:start position:0% we took that to the initial public hearing<00:54:34.299> the<00:54:34.839> response<00:54:35.380> or<00:54:36.339> feedback<00:54:36.700> we<00:54:37.029> got 00:54:37.170 --> 00:54:37.180 align:start position:0% hearing the response or feedback we got 00:54:37.180 --> 00:54:38.969 align:start position:0% hearing the response or feedback we got from<00:54:37.239> town<00:54:37.690> council<00:54:38.200> as<00:54:38.319> they<00:54:38.440> felt<00:54:38.650> that<00:54:38.799> was 00:54:38.969 --> 00:54:38.979 align:start position:0% from town council as they felt that was 00:54:38.979 --> 00:54:40.529 align:start position:0% from town council as they felt that was too<00:54:39.190> restrictive<00:54:39.789> so<00:54:39.910> it<00:54:40.029> went<00:54:40.210> back<00:54:40.359> to 00:54:40.529 --> 00:54:40.539 align:start position:0% too restrictive so it went back to 00:54:40.539 --> 00:54:47.009 align:start position:0% too restrictive so it went back to another<00:54:40.690> work<00:54:40.960> session<00:54:41.999> so<00:54:43.380> in<00:54:44.380> these<00:54:44.859> the<00:54:46.019> in 00:54:47.009 --> 00:54:47.019 align:start position:0% another work session so in these the in 00:54:47.019 --> 00:54:50.359 align:start position:0% another work session so in these the in both<00:54:47.799> the<00:54:48.039> VL<00:54:48.369> dr<00:54:48.759> and<00:54:48.940> the<00:54:49.029> LDR<00:54:49.509> areas<00:54:49.989> or<00:54:50.140> any 00:54:50.359 --> 00:54:50.369 align:start position:0% both the VL dr and the LDR areas or any 00:54:50.369 --> 00:54:52.380 align:start position:0% both the VL dr and the LDR areas or any districts<00:54:51.369> we're<00:54:51.519> still<00:54:51.789> would<00:54:52.029> be<00:54:52.180> looking 00:54:52.380 --> 00:54:52.390 align:start position:0% districts we're still would be looking 00:54:52.390 --> 00:54:57.410 align:start position:0% districts we're still would be looking at<00:54:52.719> the<00:54:52.869> density<00:54:53.549> limit<00:54:54.549> switch<00:54:54.819> in<00:54:55.119> bldr<00:54:55.690> is 00:54:57.410 --> 00:54:57.420 align:start position:0% at the density limit switch in bldr is 00:54:57.420 --> 00:55:01.469 align:start position:0% at the density limit switch in bldr is less<00:54:58.420> than<00:54:58.749> one<00:54:59.079> unit<00:54:59.410> per<00:54:59.440> acre<00:54:59.910> so<00:55:00.910> it<00:55:01.420> just 00:55:01.469 --> 00:55:01.479 align:start position:0% less than one unit per acre so it just 00:55:01.479 --> 00:55:03.089 align:start position:0% less than one unit per acre so it just provides 00:55:03.089 --> 00:55:03.099 align:start position:0% provides 00:55:03.099 --> 00:55:05.759 align:start position:0% provides a<00:55:03.130> range<00:55:03.869> so<00:55:04.869> you're<00:55:05.019> going<00:55:05.140> to<00:55:05.200> have<00:55:05.259> fewer 00:55:05.759 --> 00:55:05.769 align:start position:0% a range so you're going to have fewer 00:55:05.769 --> 00:55:08.130 align:start position:0% a range so you're going to have fewer units<00:55:06.549> in<00:55:07.089> that<00:55:07.119> area<00:55:07.479> because<00:55:07.809> the<00:55:07.930> density 00:55:08.130 --> 00:55:08.140 align:start position:0% units in that area because the density 00:55:08.140 --> 00:55:10.979 align:start position:0% units in that area because the density is<00:55:08.470> lower<00:55:08.739> but<00:55:09.460> it<00:55:09.640> maintains<00:55:10.210> the 00:55:10.979 --> 00:55:10.989 align:start position:0% is lower but it maintains the 00:55:10.989 --> 00:55:12.839 align:start position:0% is lower but it maintains the flexibility<00:55:11.890> and<00:55:11.920> looking<00:55:12.369> at<00:55:12.489> different 00:55:12.839 --> 00:55:12.849 align:start position:0% flexibility and looking at different 00:55:12.849 --> 00:55:15.269 align:start position:0% flexibility and looking at different product<00:55:13.239> types<00:55:13.269> to<00:55:13.690> have<00:55:13.869> that<00:55:14.109> that<00:55:14.680> smaller 00:55:15.269 --> 00:55:15.279 align:start position:0% product types to have that that smaller 00:55:15.279 --> 00:55:19.640 align:start position:0% product types to have that that smaller lot<00:55:15.579> size<00:55:15.989> what<00:55:16.989> the<00:55:17.499> main<00:55:18.099> thing<00:55:18.489> that<00:55:18.519> this 00:55:19.640 --> 00:55:19.650 align:start position:0% lot size what the main thing that this 00:55:19.650 --> 00:55:23.160 align:start position:0% lot size what the main thing that this amendment<00:55:20.650> would<00:55:20.979> do<00:55:21.279> and<00:55:22.089> this<00:55:22.569> is<00:55:22.630> something 00:55:23.160 --> 00:55:23.170 align:start position:0% amendment would do and this is something 00:55:23.170 --> 00:55:26.069 align:start position:0% amendment would do and this is something that<00:55:23.200> we've<00:55:23.440> seen<00:55:24.119> seemed<00:55:25.119> happen<00:55:25.720> a<00:55:25.779> number 00:55:26.069 --> 00:55:26.079 align:start position:0% that we've seen seemed happen a number 00:55:26.079 --> 00:55:28.499 align:start position:0% that we've seen seemed happen a number of<00:55:26.140> times<00:55:26.349> is<00:55:26.650> where<00:55:27.519> the<00:55:27.880> minimum<00:55:28.269> lot<00:55:28.450> size 00:55:28.499 --> 00:55:28.509 align:start position:0% of times is where the minimum lot size 00:55:28.509 --> 00:55:32.190 align:start position:0% of times is where the minimum lot size maybe<00:55:29.170> 8,000<00:55:30.039> square<00:55:30.249> feet<00:55:30.460> or<00:55:31.019> 12,000<00:55:32.019> square 00:55:32.190 --> 00:55:32.200 align:start position:0% maybe 8,000 square feet or 12,000 square 00:55:32.200 --> 00:55:36.329 align:start position:0% maybe 8,000 square feet or 12,000 square feet<00:55:32.579> often<00:55:33.579> 8,000<00:55:34.150> square<00:55:34.329> feet<00:55:34.539> but<00:55:35.339> we've 00:55:36.329 --> 00:55:36.339 align:start position:0% feet often 8,000 square feet but we've 00:55:36.339 --> 00:55:38.609 align:start position:0% feet often 8,000 square feet but we've had<00:55:36.549> a<00:55:36.579> number<00:55:36.819> of<00:55:36.999> requests<00:55:37.479> for<00:55:37.749> the<00:55:38.170> TR 00:55:38.609 --> 00:55:38.619 align:start position:0% had a number of requests for the TR 00:55:38.619 --> 00:55:42.719 align:start position:0% had a number of requests for the TR district<00:55:39.489> and<00:55:39.759> then<00:55:40.650> zoning<00:55:41.650> conditions<00:55:42.309> that 00:55:42.719 --> 00:55:42.729 align:start position:0% district and then zoning conditions that 00:55:42.729 --> 00:55:46.229 align:start position:0% district and then zoning conditions that would<00:55:42.910> limit<00:55:43.180> the<00:55:43.630> lot<00:55:44.619> size<00:55:44.979> to<00:55:45.460> 8,000 00:55:46.229 --> 00:55:46.239 align:start position:0% would limit the lot size to 8,000 00:55:46.239 --> 00:55:47.819 align:start position:0% would limit the lot size to 8,000 instead<00:55:46.660> of<00:55:46.779> the<00:55:46.869> 5,000<00:55:47.619> that<00:55:47.710> would 00:55:47.819 --> 00:55:47.829 align:start position:0% instead of the 5,000 that would 00:55:47.829 --> 00:55:50.190 align:start position:0% instead of the 5,000 that would otherwise<00:55:47.950> be<00:55:48.220> required<00:55:48.819> but<00:55:49.690> then<00:55:49.960> it's 00:55:50.190 --> 00:55:50.200 align:start position:0% otherwise be required but then it's 00:55:50.200 --> 00:55:53.729 align:start position:0% otherwise be required but then it's looking<00:55:50.650> at<00:55:50.829> perhaps<00:55:51.039> lot<00:55:51.519> width<00:55:51.880> or<00:55:52.739> setbacks 00:55:53.729 --> 00:55:53.739 align:start position:0% looking at perhaps lot width or setbacks 00:55:53.739 --> 00:55:57.210 align:start position:0% looking at perhaps lot width or setbacks and<00:55:54.460> trying<00:55:54.880> to<00:55:55.239> pull<00:55:55.599> in<00:55:55.839> some<00:55:56.289> smaller<00:55:56.799> lot 00:55:57.210 --> 00:55:57.220 align:start position:0% and trying to pull in some smaller lot 00:55:57.220 --> 00:56:01.170 align:start position:0% and trying to pull in some smaller lot wits<00:55:57.549> and<00:55:57.789> smaller<00:55:58.059> setbacks<00:55:59.039> so<00:56:00.039> this<00:56:00.910> would 00:56:01.170 --> 00:56:01.180 align:start position:0% wits and smaller setbacks so this would 00:56:01.180 --> 00:56:06.299 align:start position:0% wits and smaller setbacks so this would prevent<00:56:01.749> the<00:56:03.509> less<00:56:04.509> restrictive<00:56:05.319> dimensional 00:56:06.299 --> 00:56:06.309 align:start position:0% prevent the less restrictive dimensional 00:56:06.309 --> 00:56:08.219 align:start position:0% prevent the less restrictive dimensional standards<00:56:06.849> associated<00:56:07.479> with<00:56:07.749> the<00:56:07.869> TR 00:56:08.219 --> 00:56:08.229 align:start position:0% standards associated with the TR 00:56:08.229 --> 00:56:11.279 align:start position:0% standards associated with the TR district<00:56:08.859> from<00:56:09.549> being<00:56:09.819> a<00:56:09.940> from<00:56:10.660> kind<00:56:10.989> of<00:56:11.109> being 00:56:11.279 --> 00:56:11.289 align:start position:0% district from being a from kind of being 00:56:11.289 --> 00:56:13.079 align:start position:0% district from being a from kind of being mixed<00:56:11.589> and<00:56:11.920> matched<00:56:12.099> in<00:56:12.489> where<00:56:12.729> you<00:56:12.759> have<00:56:12.999> the 00:56:13.079 --> 00:56:13.089 align:start position:0% mixed and matched in where you have the 00:56:13.089 --> 00:56:15.959 align:start position:0% mixed and matched in where you have the 8,000<00:56:13.660> square<00:56:13.839> foot<00:56:14.019> lot<00:56:14.079> sand<00:56:14.680> and<00:56:14.859> by<00:56:15.670> having 00:56:15.959 --> 00:56:15.969 align:start position:0% 8,000 square foot lot sand and by having 00:56:15.969 --> 00:56:18.450 align:start position:0% 8,000 square foot lot sand and by having that<00:56:16.269> better<00:56:16.869> relationship<00:56:17.799> between<00:56:18.219> all<00:56:18.430> of 00:56:18.450 --> 00:56:18.460 align:start position:0% that better relationship between all of 00:56:18.460 --> 00:56:20.729 align:start position:0% that better relationship between all of your<00:56:18.729> lot<00:56:18.910> dimensions<00:56:19.150> even<00:56:19.839> in<00:56:20.289> an<00:56:20.529> area 00:56:20.729 --> 00:56:20.739 align:start position:0% your lot dimensions even in an area 00:56:20.739 --> 00:56:23.809 align:start position:0% your lot dimensions even in an area that's<00:56:21.039> low<00:56:21.339> density<00:56:21.969> it's<00:56:22.539> more<00:56:22.869> predictable 00:56:23.809 --> 00:56:23.819 align:start position:0% that's low density it's more predictable 00:56:23.819 --> 00:56:27.029 align:start position:0% that's low density it's more predictable and<00:56:24.989> you<00:56:25.989> know<00:56:26.170> you're<00:56:26.380> always<00:56:26.710> going<00:56:26.920> to<00:56:26.979> have 00:56:27.029 --> 00:56:27.039 align:start position:0% and you know you're always going to have 00:56:27.039 --> 00:56:30.299 align:start position:0% and you know you're always going to have your<00:56:27.369> density<00:56:27.579> limits<00:56:28.269> and<00:56:28.799> and<00:56:29.799> then<00:56:30.190> at 00:56:30.299 --> 00:56:30.309 align:start position:0% your density limits and and then at 00:56:30.309 --> 00:56:31.920 align:start position:0% your density limits and and then at least<00:56:30.430> you'll<00:56:30.700> know<00:56:30.759> that<00:56:31.029> your<00:56:31.150> lot<00:56:31.359> sizes 00:56:31.920 --> 00:56:31.930 align:start position:0% least you'll know that your lot sizes 00:56:31.930 --> 00:56:33.539 align:start position:0% least you'll know that your lot sizes and<00:56:32.140> your<00:56:32.259> dimensions<00:56:32.739> and<00:56:32.920> your<00:56:33.009> setbacks 00:56:33.539 --> 00:56:33.549 align:start position:0% and your dimensions and your setbacks 00:56:33.549 --> 00:56:38.910 align:start position:0% and your dimensions and your setbacks are<00:56:33.880> all<00:56:34.029> going<00:56:34.269> to<00:56:34.329> be<00:56:34.930> in<00:56:35.019> scale<00:56:37.739> any<00:56:38.739> other 00:56:38.910 --> 00:56:38.920 align:start position:0% are all going to be in scale any other 00:56:38.920 --> 00:56:45.479 align:start position:0% are all going to be in scale any other questions<00:56:42.479> Mary<00:56:43.479> if<00:56:43.749> you<00:56:43.989> would<00:56:44.249> I'm<00:56:45.249> not<00:56:45.430> sure 00:56:45.479 --> 00:56:45.489 align:start position:0% questions Mary if you would I'm not sure 00:56:45.489 --> 00:56:47.309 align:start position:0% questions Mary if you would I'm not sure everybody<00:56:45.849> on<00:56:46.329> the<00:56:46.420> board<00:56:46.690> is<00:56:46.869> aware<00:56:47.200> of<00:56:47.229> the 00:56:47.309 --> 00:56:47.319 align:start position:0% everybody on the board is aware of the 00:56:47.319 --> 00:56:53.219 align:start position:0% everybody on the board is aware of the VLC<00:56:47.739> are<00:56:48.599> versus<00:56:49.599> the<00:56:49.779> veal<00:56:49.989> dr<00:56:51.119> areas<00:56:52.229> even 00:56:53.219 --> 00:56:53.229 align:start position:0% VLC are versus the veal dr areas even 00:56:53.229 --> 00:56:55.920 align:start position:0% VLC are versus the veal dr areas even and<00:56:53.890> i<00:56:54.069> live<00:56:54.700> in<00:56:54.729> one<00:56:54.999> of<00:56:55.029> those<00:56:55.239> areas<00:56:55.690> and<00:56:55.809> i 00:56:55.920 --> 00:56:55.930 align:start position:0% and i live in one of those areas and i 00:56:55.930 --> 00:56:58.920 align:start position:0% and i live in one of those areas and i was<00:56:56.079> a<00:56:56.109> little<00:56:56.380> bit<00:56:56.559> confused<00:56:57.130> right<00:56:57.549> yes<00:56:58.539> ok 00:56:58.920 --> 00:56:58.930 align:start position:0% was a little bit confused right yes ok 00:56:58.930 --> 00:57:01.920 align:start position:0% was a little bit confused right yes ok so<00:56:58.989> the<00:56:59.410> was<00:56:59.559> it<00:56:59.739> feels<00:56:59.979> here<00:57:00.249> the<00:57:00.969> veal<00:57:01.210> for 00:57:01.920 --> 00:57:01.930 align:start position:0% so the was it feels here the veal for 00:57:01.930 --> 00:57:03.400 align:start position:0% so the was it feels here the veal for example<00:57:02.410> the 00:57:03.400 --> 00:57:03.410 align:start position:0% example the 00:57:03.410 --> 00:57:06.210 align:start position:0% example the and<00:57:03.740> we<00:57:03.859> saw<00:57:04.069> on<00:57:04.220> ridgeback<00:57:04.640> road<00:57:05.170> recently 00:57:06.210 --> 00:57:06.220 align:start position:0% and we saw on ridgeback road recently 00:57:06.220 --> 00:57:10.210 align:start position:0% and we saw on ridgeback road recently came<00:57:07.220> in<00:57:07.400> with<00:57:07.549> an<00:57:07.700> r<00:57:07.880> 12<00:57:08.559> conditional-use<00:57:09.559> and 00:57:10.210 --> 00:57:10.220 align:start position:0% came in with an r 12 conditional-use and 00:57:10.220 --> 00:57:14.770 align:start position:0% came in with an r 12 conditional-use and they<00:57:10.549> are<00:57:10.609> in<00:57:10.910> the<00:57:11.089> VLC<00:57:11.480> arf<00:57:12.289> and<00:57:13.390> when<00:57:14.390> I<00:57:14.420> read 00:57:14.770 --> 00:57:14.780 align:start position:0% they are in the VLC arf and when I read 00:57:14.780 --> 00:57:17.920 align:start position:0% they are in the VLC arf and when I read this<00:57:14.990> I<00:57:15.049> was<00:57:15.619> thinking<00:57:16.039> all<00:57:16.250> the<00:57:16.700> ldr<00:57:17.180> was<00:57:17.510> that 00:57:17.920 --> 00:57:17.930 align:start position:0% this I was thinking all the ldr was that 00:57:17.930 --> 00:57:19.839 align:start position:0% this I was thinking all the ldr was that and<00:57:18.349> then<00:57:18.500> you<00:57:18.650> could<00:57:18.799> put<00:57:19.010> this<00:57:19.160> conditional 00:57:19.839 --> 00:57:19.849 align:start position:0% and then you could put this conditional 00:57:19.849 --> 00:57:23.049 align:start position:0% and then you could put this conditional overlay<00:57:20.270> so<00:57:20.440> there<00:57:21.440> is<00:57:21.710> in<00:57:22.220> the<00:57:22.460> southwest 00:57:23.049 --> 00:57:23.059 align:start position:0% overlay so there is in the southwest 00:57:23.059 --> 00:57:27.250 align:start position:0% overlay so there is in the southwest area<00:57:23.510> plan<00:57:23.990> there<00:57:24.619> is<00:57:25.150> portion<00:57:26.150> in<00:57:26.329> the<00:57:26.480> war 00:57:27.250 --> 00:57:27.260 align:start position:0% area plan there is portion in the war 00:57:27.260 --> 00:57:29.349 align:start position:0% area plan there is portion in the war western<00:57:27.920> portion<00:57:28.339> of<00:57:28.400> the<00:57:28.520> southwest<00:57:29.150> area 00:57:29.349 --> 00:57:29.359 align:start position:0% western portion of the southwest area 00:57:29.359 --> 00:57:33.400 align:start position:0% western portion of the southwest area plan<00:57:29.710> that<00:57:30.710> has<00:57:31.130> an<00:57:31.549> overlay<00:57:32.390> that<00:57:32.839> called<00:57:33.260> the 00:57:33.400 --> 00:57:33.410 align:start position:0% plan that has an overlay that called the 00:57:33.410 --> 00:57:35.440 align:start position:0% plan that has an overlay that called the conservation<00:57:33.940> residential<00:57:34.940> overlay 00:57:35.440 --> 00:57:35.450 align:start position:0% conservation residential overlay 00:57:35.450 --> 00:57:40.630 align:start position:0% conservation residential overlay district<00:57:36.020> the<00:57:36.980> plan<00:57:37.339> designation<00:57:39.640> under 00:57:40.630 --> 00:57:40.640 align:start position:0% district the plan designation under 00:57:40.640 --> 00:57:44.559 align:start position:0% district the plan designation under underneath<00:57:41.359> that<00:57:42.789> where<00:57:43.789> that<00:57:44.059> overlay 00:57:44.559 --> 00:57:44.569 align:start position:0% underneath that where that overlay 00:57:44.569 --> 00:57:46.720 align:start position:0% underneath that where that overlay district<00:57:45.170> would<00:57:45.530> be<00:57:45.770> applied<00:57:46.099> when<00:57:46.520> as 00:57:46.720 --> 00:57:46.730 align:start position:0% district would be applied when as 00:57:46.730 --> 00:57:51.180 align:start position:0% district would be applied when as properties<00:57:47.299> come<00:57:47.780> in<00:57:47.960> to<00:57:48.140> be<00:57:48.319> developed<00:57:50.170> the 00:57:51.180 --> 00:57:51.190 align:start position:0% properties come in to be developed the 00:57:51.190 --> 00:57:54.660 align:start position:0% properties come in to be developed the underlying<00:57:52.299> plan<00:57:53.299> designation<00:57:53.630> is<00:57:54.349> either 00:57:54.660 --> 00:57:54.670 align:start position:0% underlying plan designation is either 00:57:54.670 --> 00:58:00.910 align:start position:0% underlying plan designation is either VLC<00:57:55.670> typically<00:57:56.420> be<00:57:56.599> LCR<00:57:57.380> or<00:57:57.920> or<00:57:59.230> LCR<00:58:00.230> and<00:58:00.619> the 00:58:00.910 --> 00:58:00.920 align:start position:0% VLC typically be LCR or or LCR and the 00:58:00.920 --> 00:58:03.640 align:start position:0% VLC typically be LCR or or LCR and the difference<00:58:01.339> between<00:58:01.460> the<00:58:01.789> L<00:58:01.970> and<00:58:02.210> to<00:58:02.329> see<00:58:02.650> in 00:58:03.640 --> 00:58:03.650 align:start position:0% difference between the L and to see in 00:58:03.650 --> 00:58:08.019 align:start position:0% difference between the L and to see in those<00:58:04.960> names<00:58:05.960> has<00:58:06.380> indicates<00:58:07.250> that<00:58:07.400> it's<00:58:07.730> in 00:58:08.019 --> 00:58:08.029 align:start position:0% those names has indicates that it's in 00:58:08.029 --> 00:58:10.510 align:start position:0% those names has indicates that it's in the<00:58:08.299> conservation<00:58:08.799> residential<00:58:09.799> area<00:58:10.130> so<00:58:10.400> to 00:58:10.510 --> 00:58:10.520 align:start position:0% the conservation residential area so to 00:58:10.520 --> 00:58:12.460 align:start position:0% the conservation residential area so to seize<00:58:10.700> for<00:58:10.880> conservation<00:58:11.390> law<00:58:11.480> yeah<00:58:11.690> so<00:58:12.170> it's 00:58:12.460 --> 00:58:12.470 align:start position:0% seize for conservation law yeah so it's 00:58:12.470 --> 00:58:15.670 align:start position:0% seize for conservation law yeah so it's so<00:58:12.920> and<00:58:13.190> that<00:58:13.789> is<00:58:14.059> not<00:58:14.359> reflected<00:58:15.109> in<00:58:15.109> this<00:58:15.410> in 00:58:15.670 --> 00:58:15.680 align:start position:0% so and that is not reflected in this in 00:58:15.680 --> 00:58:17.410 align:start position:0% so and that is not reflected in this in this<00:58:15.980> table<00:58:16.250> we're<00:58:16.549> not<00:58:16.700> making<00:58:17.119> any 00:58:17.410 --> 00:58:17.420 align:start position:0% this table we're not making any 00:58:17.420 --> 00:58:23.799 align:start position:0% this table we're not making any statements<00:58:18.410> or<00:58:21.490> the<00:58:22.490> clarification<00:58:23.390> related 00:58:23.799 --> 00:58:23.809 align:start position:0% statements or the clarification related 00:58:23.809 --> 00:58:27.910 align:start position:0% statements or the clarification related to<00:58:24.490> the<00:58:25.490> VLC<00:58:25.880> are<00:58:26.390> because<00:58:26.839> it's<00:58:26.869> subject<00:58:27.829> to 00:58:27.910 --> 00:58:27.920 align:start position:0% to the VLC are because it's subject to 00:58:27.920 --> 00:58:31.359 align:start position:0% to the VLC are because it's subject to its<00:58:28.609> own<00:58:28.849> set<00:58:29.119> of<00:58:29.150> standards<00:58:29.809> where<00:58:30.200> you<00:58:31.039> can 00:58:31.359 --> 00:58:31.369 align:start position:0% its own set of standards where you can 00:58:31.369 --> 00:58:34.510 align:start position:0% its own set of standards where you can you<00:58:32.150> can<00:58:32.390> develop<00:58:32.630> in<00:58:32.990> the<00:58:33.140> in<00:58:33.529> those<00:58:33.950> areas 00:58:34.510 --> 00:58:34.520 align:start position:0% you can develop in the in those areas 00:58:34.520 --> 00:58:36.609 align:start position:0% you can develop in the in those areas under<00:58:34.880> the<00:58:35.000> are<00:58:35.119> 40<00:58:35.510> zoning<00:58:35.990> and<00:58:36.140> if<00:58:36.289> you<00:58:36.410> save 00:58:36.609 --> 00:58:36.619 align:start position:0% under the are 40 zoning and if you save 00:58:36.619 --> 00:58:39.250 align:start position:0% under the are 40 zoning and if you save additional<00:58:36.799> open<00:58:37.520> space<00:58:37.819> you<00:58:38.480> get<00:58:38.690> a<00:58:38.720> density 00:58:39.250 --> 00:58:39.260 align:start position:0% additional open space you get a density 00:58:39.260 --> 00:58:41.700 align:start position:0% additional open space you get a density bonus<00:58:39.680> and<00:58:39.890> there's<00:58:40.039> limitations<00:58:40.549> on 00:58:41.700 --> 00:58:41.710 align:start position:0% bonus and there's limitations on 00:58:41.710 --> 00:58:43.990 align:start position:0% bonus and there's limitations on depending<00:58:42.710> on<00:58:42.829> how<00:58:42.980> much<00:58:43.130> open<00:58:43.520> space<00:58:43.549> you 00:58:43.990 --> 00:58:44.000 align:start position:0% depending on how much open space you 00:58:44.000 --> 00:58:47.049 align:start position:0% depending on how much open space you have<00:58:44.029> with<00:58:44.480> what<00:58:44.720> your<00:58:45.220> density<00:58:46.220> and<00:58:46.730> your<00:58:46.880> lot 00:58:47.049 --> 00:58:47.059 align:start position:0% have with what your density and your lot 00:58:47.059 --> 00:58:50.650 align:start position:0% have with what your density and your lot sizes<00:58:47.599> can<00:58:47.779> be<00:58:48.039> so<00:58:49.039> there's<00:58:49.490> already<00:58:49.789> a<00:58:50.119> table 00:58:50.650 --> 00:58:50.660 align:start position:0% sizes can be so there's already a table 00:58:50.660 --> 00:58:53.170 align:start position:0% sizes can be so there's already a table that<00:58:51.460> ordinance<00:58:52.460> section<00:58:52.849> it<00:58:52.970> deals 00:58:53.170 --> 00:58:53.180 align:start position:0% that ordinance section it deals 00:58:53.180 --> 00:58:55.029 align:start position:0% that ordinance section it deals specifically<00:58:53.960> with<00:58:54.140> that<00:58:54.470> conservation 00:58:55.029 --> 00:58:55.039 align:start position:0% specifically with that conservation 00:58:55.039 --> 00:58:57.819 align:start position:0% specifically with that conservation residential<00:58:55.760> overlay<00:58:56.180> area<00:58:56.539> and<00:58:56.960> then<00:58:57.470> it<00:58:57.619> has 00:58:57.819 --> 00:58:57.829 align:start position:0% residential overlay area and then it has 00:58:57.829 --> 00:58:59.620 align:start position:0% residential overlay area and then it has its<00:58:58.069> own<00:58:58.279> plan<00:58:58.640> designations<00:58:59.480> that 00:58:59.620 --> 00:58:59.630 align:start position:0% its own plan designations that 00:58:59.630 --> 00:59:01.990 align:start position:0% its own plan designations that correspond<00:59:00.410> with<00:59:00.529> it<00:59:00.829> and<00:59:01.490> the<00:59:01.609> reason<00:59:01.760> I 00:59:01.990 --> 00:59:02.000 align:start position:0% correspond with it and the reason I 00:59:02.000 --> 00:59:05.019 align:start position:0% correspond with it and the reason I bring<00:59:02.210> that<00:59:02.470> a<00:59:03.470> couple<00:59:04.160> of<00:59:04.220> things<00:59:04.520> first<00:59:04.819> of 00:59:05.019 --> 00:59:05.029 align:start position:0% bring that a couple of things first of 00:59:05.029 --> 00:59:07.259 align:start position:0% bring that a couple of things first of all<00:59:05.210> in<00:59:05.450> the<00:59:05.630> VLC<00:59:05.960> are<00:59:06.380> the<00:59:06.529> minimum 00:59:07.259 --> 00:59:07.269 align:start position:0% all in the VLC are the minimum 00:59:07.269 --> 00:59:09.509 align:start position:0% all in the VLC are the minimum sighs<00:59:07.449> no<00:59:07.899> matter<00:59:08.049> what<00:59:08.259> you<00:59:08.289> do<00:59:08.499> is<00:59:08.619> 15,000 00:59:09.509 --> 00:59:09.519 align:start position:0% sighs no matter what you do is 15,000 00:59:09.519 --> 00:59:12.809 align:start position:0% sighs no matter what you do is 15,000 square<00:59:09.759> feet<00:59:10.439> but<00:59:11.439> the<00:59:11.589> second<00:59:12.039> thing<00:59:12.219> is<00:59:12.519> that 00:59:12.809 --> 00:59:12.819 align:start position:0% square feet but the second thing is that 00:59:12.819 --> 00:59:15.749 align:start position:0% square feet but the second thing is that if<00:59:12.969> you<00:59:13.209> opt<00:59:13.599> to<00:59:14.019> go<00:59:14.229> down<00:59:14.499> to<00:59:14.529> that<00:59:14.759> 15,000 00:59:15.749 --> 00:59:15.759 align:start position:0% if you opt to go down to that 15,000 00:59:15.759 --> 00:59:17.419 align:start position:0% if you opt to go down to that 15,000 square<00:59:16.029> feet<00:59:16.299> there<00:59:16.869> are<00:59:17.049> additional 00:59:17.419 --> 00:59:17.429 align:start position:0% square feet there are additional 00:59:17.429 --> 00:59:19.499 align:start position:0% square feet there are additional protections<00:59:18.429> I<00:59:18.549> guess<00:59:18.759> for<00:59:18.969> the<00:59:19.089> rest<00:59:19.269> of<00:59:19.390> the 00:59:19.499 --> 00:59:19.509 align:start position:0% protections I guess for the rest of the 00:59:19.509 --> 00:59:21.839 align:start position:0% protections I guess for the rest of the neighborhood<00:59:19.689> and<00:59:20.019> that<00:59:20.409> your<00:59:20.849> streetscape 00:59:21.839 --> 00:59:21.849 align:start position:0% neighborhood and that your streetscape 00:59:21.849 --> 00:59:24.749 align:start position:0% neighborhood and that your streetscape has<00:59:22.149> to<00:59:22.329> go<00:59:22.449> up<00:59:22.539> to<00:59:22.689> 80<00:59:22.929> feet<00:59:23.259> right<00:59:23.529> doesn't<00:59:24.519> it 00:59:24.749 --> 00:59:24.759 align:start position:0% has to go up to 80 feet right doesn't it 00:59:24.759 --> 00:59:28.559 align:start position:0% has to go up to 80 feet right doesn't it have<00:59:24.939> to<00:59:25.119> go<00:59:25.209> back<00:59:25.419> from<00:59:25.719> 50<00:59:26.259> to<00:59:26.289> 80<00:59:26.829> I<00:59:27.569> don't 00:59:28.559 --> 00:59:28.569 align:start position:0% have to go back from 50 to 80 I don't 00:59:28.569 --> 00:59:30.749 align:start position:0% have to go back from 50 to 80 I don't recall<00:59:28.749> that<00:59:29.380> there<00:59:29.709> are<00:59:29.890> additional<00:59:30.189> buffs 00:59:30.749 --> 00:59:30.759 align:start position:0% recall that there are additional buffs 00:59:30.759 --> 00:59:35.189 align:start position:0% recall that there are additional buffs of<00:59:30.969> protections<00:59:32.009> so<00:59:33.359> you<00:59:34.359> know<00:59:34.479> I<00:59:34.719> would<00:59:35.019> have 00:59:35.189 --> 00:59:35.199 align:start position:0% of protections so you know I would have 00:59:35.199 --> 00:59:37.349 align:start position:0% of protections so you know I would have almost<00:59:35.469> preferred<00:59:36.130> to<00:59:36.309> have<00:59:36.339> seen<00:59:36.609> VLC<00:59:37.209> are 00:59:37.349 --> 00:59:37.359 align:start position:0% almost preferred to have seen VLC are 00:59:37.359 --> 00:59:40.109 align:start position:0% almost preferred to have seen VLC are laid<00:59:37.779> on<00:59:37.929> top<00:59:37.959> of<00:59:38.349> all<00:59:38.499> the<00:59:38.619> VL<00:59:38.859> dr<00:59:39.279> areas 00:59:40.109 --> 00:59:40.119 align:start position:0% laid on top of all the VL dr areas 00:59:40.119 --> 00:59:43.409 align:start position:0% laid on top of all the VL dr areas because<00:59:40.449> you<00:59:41.109> know<00:59:41.229> when<00:59:41.380> i<00:59:41.409> read<00:59:41.739> this<00:59:42.419> you 00:59:43.409 --> 00:59:43.419 align:start position:0% because you know when i read this you 00:59:43.419 --> 00:59:47.009 align:start position:0% because you know when i read this you know<00:59:43.949> number<00:59:44.949> two<00:59:45.159> on<00:59:45.609> the<00:59:45.669> background<00:59:46.539> the 00:59:47.009 --> 00:59:47.019 align:start position:0% know number two on the background the 00:59:47.019 --> 00:59:49.079 align:start position:0% know number two on the background the reason<00:59:47.319> we're<00:59:47.439> doing<00:59:47.589> this<00:59:47.769> is<00:59:48.219> to<00:59:48.549> set<00:59:48.789> lot 00:59:49.079 --> 00:59:49.089 align:start position:0% reason we're doing this is to set lot 00:59:49.089 --> 00:59:52.049 align:start position:0% reason we're doing this is to set lot size<00:59:49.589> expectations<00:59:50.589> based<00:59:51.099> on<00:59:51.459> the<00:59:51.609> land<00:59:51.849> use 00:59:52.049 --> 00:59:52.059 align:start position:0% size expectations based on the land use 00:59:52.059 --> 00:59:55.079 align:start position:0% size expectations based on the land use plan<00:59:52.499> for<00:59:53.499> neighbors<00:59:53.919> and<00:59:54.159> if<00:59:54.579> we're<00:59:54.789> saying 00:59:55.079 --> 00:59:55.089 align:start position:0% plan for neighbors and if we're saying 00:59:55.089 --> 00:59:57.329 align:start position:0% plan for neighbors and if we're saying you<00:59:55.299> can<00:59:55.449> build<00:59:55.659> 8,000<00:59:56.289> square<00:59:56.499> foot<00:59:56.679> lots<00:59:56.979> and 00:59:57.329 --> 00:59:57.339 align:start position:0% you can build 8,000 square foot lots and 00:59:57.339 --> 00:59:59.599 align:start position:0% you can build 8,000 square foot lots and I<00:59:57.399> bldr<00:59:57.939> I<00:59:57.969> don't<00:59:58.239> think<00:59:58.390> we've<00:59:58.509> met<00:59:58.539> that<00:59:58.869> goal 00:59:59.599 --> 00:59:59.609 align:start position:0% I bldr I don't think we've met that goal 00:59:59.609 --> 01:00:03.179 align:start position:0% I bldr I don't think we've met that goal now<01:00:00.609> it<01:00:00.909> may<01:00:01.209> make<01:00:01.419> a<01:00:01.449> lot<01:00:01.689> of<01:00:01.719> sense<01:00:02.189> because 01:00:03.179 --> 01:00:03.189 align:start position:0% now it may make a lot of sense because 01:00:03.189 --> 01:00:05.339 align:start position:0% now it may make a lot of sense because you're<01:00:03.579> you<01:00:04.089> know<01:00:04.209> if<01:00:04.390> you<01:00:04.539> cluster 01:00:05.339 --> 01:00:05.349 align:start position:0% you're you know if you cluster 01:00:05.349 --> 01:00:08.039 align:start position:0% you're you know if you cluster everything<01:00:06.069> in<01:00:06.219> one<01:00:06.399> little<01:00:06.609> spot<01:00:06.939> you<01:00:07.269> reduce 01:00:08.039 --> 01:00:08.049 align:start position:0% everything in one little spot you reduce 01:00:08.049 --> 01:00:12.029 align:start position:0% everything in one little spot you reduce the<01:00:08.079> impact<01:00:08.589> of<01:00:08.739> the<01:00:08.859> infrastructure<01:00:09.579> etc<01:00:11.039> but 01:00:12.029 --> 01:00:12.039 align:start position:0% the impact of the infrastructure etc but 01:00:12.039 --> 01:00:14.519 align:start position:0% the impact of the infrastructure etc but you<01:00:12.489> know<01:00:13.269> what<01:00:13.479> if<01:00:13.630> they<01:00:13.809> choose<01:00:14.049> to<01:00:14.229> do<01:00:14.349> that 01:00:14.519 --> 01:00:14.529 align:start position:0% you know what if they choose to do that 01:00:14.529 --> 01:00:15.870 align:start position:0% you know what if they choose to do that right<01:00:14.559> up<01:00:14.919> against<01:00:15.309> the<01:00:15.369> road<01:00:15.609> where 01:00:15.870 --> 01:00:15.880 align:start position:0% right up against the road where 01:00:15.880 --> 01:00:18.749 align:start position:0% right up against the road where everything<01:00:15.909> else<01:00:16.619> you<01:00:17.619> know<01:00:17.649> is<01:00:18.069> trees<01:00:18.489> and 01:00:18.749 --> 01:00:18.759 align:start position:0% everything else you know is trees and 01:00:18.759 --> 01:00:20.849 align:start position:0% everything else you know is trees and woods<01:00:18.939> and<01:00:19.359> whatever<01:00:19.659> people<01:00:20.049> expected<01:00:20.679> in 01:00:20.849 --> 01:00:20.859 align:start position:0% woods and whatever people expected in 01:00:20.859 --> 01:00:25.379 align:start position:0% woods and whatever people expected in bldr<01:00:21.369> so<01:00:21.989> once<01:00:22.989> again<01:00:23.169> I<01:00:23.380> find<01:00:23.589> that<01:00:24.099> I<01:00:24.489> wish<01:00:25.209> we 01:00:25.379 --> 01:00:25.389 align:start position:0% bldr so once again I find that I wish we 01:00:25.389 --> 01:00:27.089 align:start position:0% bldr so once again I find that I wish we had<01:00:25.569> just<01:00:25.839> a<01:00:25.959> little<01:00:26.289> bit<01:00:26.469> more<01:00:26.799> protection 01:00:27.089 --> 01:00:27.099 align:start position:0% had just a little bit more protection 01:00:27.099 --> 01:00:31.139 align:start position:0% had just a little bit more protection here<01:00:27.699> when<01:00:27.939> you<01:00:28.059> went<01:00:28.269> down<01:00:28.509> to<01:00:29.279> past<01:00:30.279> art<01:00:30.759> you 01:00:31.139 --> 01:00:31.149 align:start position:0% here when you went down to past art you 01:00:31.149 --> 01:00:34.949 align:start position:0% here when you went down to past art you know<01:00:31.329> to<01:00:31.959> r12<01:00:32.439> r8<01:00:33.099> there<01:00:33.939> would<01:00:34.119> be<01:00:34.149> additional 01:00:34.949 --> 01:00:34.959 align:start position:0% know to r12 r8 there would be additional 01:00:34.959 --> 01:00:41.470 align:start position:0% know to r12 r8 there would be additional buffering<01:00:35.559> requirements 01:00:41.470 --> 01:00:41.480 align:start position:0% 01:00:41.480 --> 01:00:44.570 align:start position:0% I<01:00:42.480> mean<01:00:42.900> to<01:00:43.200> me<01:00:43.350> r8<01:00:43.740> just<01:00:44.040> seems<01:00:44.250> kind<01:00:44.490> of 01:00:44.570 --> 01:00:44.580 align:start position:0% I mean to me r8 just seems kind of 01:00:44.580 --> 01:00:46.160 align:start position:0% I mean to me r8 just seems kind of ludicrous<01:00:44.760> but<01:00:45.240> when<01:00:45.390> I<01:00:45.420> think<01:00:45.720> about<01:00:45.780> it<01:00:46.050> from 01:00:46.160 --> 01:00:46.170 align:start position:0% ludicrous but when I think about it from 01:00:46.170 --> 01:00:52.090 align:start position:0% ludicrous but when I think about it from an<01:00:46.350> environmental<01:00:46.650> point<01:00:48.350> it<01:00:49.350> makes<01:00:49.590> sense 01:00:52.090 --> 01:00:52.100 align:start position:0% 01:00:52.100 --> 01:00:56.360 align:start position:0% any<01:00:53.100> other<01:00:53.250> questions<01:00:53.760> or<01:00:53.940> comments<01:00:54.210> you<01:00:55.370> had 01:00:56.360 --> 01:00:56.370 align:start position:0% any other questions or comments you had 01:00:56.370 --> 01:00:59.360 align:start position:0% any other questions or comments you had a<01:00:56.400> look<01:00:56.520> I<01:00:56.670> get<01:00:57.060> a<01:00:57.090> question<01:00:57.510> I<01:00:57.660> don't<01:00:58.250> quick<01:00:59.250> is 01:00:59.360 --> 01:00:59.370 align:start position:0% a look I get a question I don't quick is 01:00:59.370 --> 01:01:01.310 align:start position:0% a look I get a question I don't quick is how<01:00:59.670> much<01:00:59.820> of<01:00:59.880> the<01:01:00.180> south<01:01:00.420> is<01:01:00.570> basically<01:01:01.170> with 01:01:01.310 --> 01:01:01.320 align:start position:0% how much of the south is basically with 01:01:01.320 --> 01:01:03.260 align:start position:0% how much of the south is basically with the<01:01:01.350> most<01:01:01.980> air<01:01:02.190> we<01:01:02.340> have<01:01:02.490> left<01:01:02.760> is<01:01:02.940> down<01:01:03.120> in<01:01:03.240> the 01:01:03.260 --> 01:01:03.270 align:start position:0% the most air we have left is down in the 01:01:03.270 --> 01:01:04.460 align:start position:0% the most air we have left is down in the southwest<01:01:03.480> area<01:01:03.810> so<01:01:03.960> I'm<01:01:04.020> glad<01:01:04.230> you<01:01:04.320> mentioned 01:01:04.460 --> 01:01:04.470 align:start position:0% southwest area so I'm glad you mentioned 01:01:04.470 --> 01:01:06.440 align:start position:0% southwest area so I'm glad you mentioned that<01:01:04.620> conservation<01:01:05.100> overly<01:01:05.580> how<01:01:06.270> much 01:01:06.440 --> 01:01:06.450 align:start position:0% that conservation overly how much 01:01:06.450 --> 01:01:08.420 align:start position:0% that conservation overly how much percentage<01:01:07.020> of<01:01:07.170> that<01:01:07.200> Newt<01:01:07.530> that<01:01:07.950> southwest 01:01:08.420 --> 01:01:08.430 align:start position:0% percentage of that Newt that southwest 01:01:08.430 --> 01:01:11.000 align:start position:0% percentage of that Newt that southwest area<01:01:08.610> is<01:01:08.880> in<01:01:09.060> the<01:01:09.180> top<01:01:09.560> conservation<01:01:10.560> overlay 01:01:11.000 --> 01:01:11.010 align:start position:0% area is in the top conservation overlay 01:01:11.010 --> 01:01:13.340 align:start position:0% area is in the top conservation overlay I<01:01:11.280> know<01:01:12.030> it's<01:01:12.210> a<01:01:12.270> really<01:01:12.450> tough<01:01:12.750> mission<01:01:13.230> I'm 01:01:13.340 --> 01:01:13.350 align:start position:0% I know it's a really tough mission I'm 01:01:13.350 --> 01:01:17.240 align:start position:0% I know it's a really tough mission I'm sorry<01:01:15.080> because<01:01:16.080> I'm<01:01:16.260> just<01:01:16.380> that's<01:01:17.010> that's 01:01:17.240 --> 01:01:17.250 align:start position:0% sorry because I'm just that's that's 01:01:17.250 --> 01:01:18.740 align:start position:0% sorry because I'm just that's that's where<01:01:17.370> I'm<01:01:17.430> worried<01:01:17.670> about<01:01:17.700> right<01:01:17.850> now<01:01:18.060> so<01:01:18.720> I 01:01:18.740 --> 01:01:18.750 align:start position:0% where I'm worried about right now so I 01:01:18.750 --> 01:01:20.630 align:start position:0% where I'm worried about right now so I don't<01:01:18.810> want<01:01:19.110> I'm<01:01:19.800> there<01:01:20.190> with<01:01:20.310> you<01:01:20.370> worried 01:01:20.630 --> 01:01:20.640 align:start position:0% don't want I'm there with you worried 01:01:20.640 --> 01:01:23.260 align:start position:0% don't want I'm there with you worried about<01:01:20.700> the<01:01:21.140> balance<01:01:22.140> of<01:01:22.260> lot<01:01:22.500> size<01:01:22.740> versus 01:01:23.260 --> 01:01:23.270 align:start position:0% about the balance of lot size versus 01:01:23.270 --> 01:01:26.780 align:start position:0% about the balance of lot size versus environmental<01:01:24.270> versus<01:01:25.040> density<01:01:26.040> so<01:01:26.580> I'm<01:01:26.670> glad 01:01:26.780 --> 01:01:26.790 align:start position:0% environmental versus density so I'm glad 01:01:26.790 --> 01:01:28.280 align:start position:0% environmental versus density so I'm glad to<01:01:26.970> hear<01:01:27.150> that<01:01:27.300> I<01:01:27.570> forgot<01:01:27.960> all<01:01:28.080> about<01:01:28.110> that 01:01:28.280 --> 01:01:28.290 align:start position:0% to hear that I forgot all about that 01:01:28.290 --> 01:01:31.300 align:start position:0% to hear that I forgot all about that part<01:01:29.060> yeah<01:01:30.060> it<01:01:30.240> just<01:01:30.300> depends<01:01:30.810> on<01:01:30.900> what<01:01:31.110> the 01:01:31.300 --> 01:01:31.310 align:start position:0% part yeah it just depends on what the 01:01:31.310 --> 01:01:34.430 align:start position:0% part yeah it just depends on what the objective<01:01:32.310> here<01:01:32.610> is<01:01:32.640> so<01:01:33.180> I<01:01:33.420> could<01:01:33.660> almost<01:01:33.930> go 01:01:34.430 --> 01:01:34.440 align:start position:0% objective here is so I could almost go 01:01:34.440 --> 01:01:37.040 align:start position:0% objective here is so I could almost go for<01:01:34.740> this<01:01:34.890> if<01:01:35.340> we<01:01:35.640> treated<01:01:36.030> any<01:01:36.390> of<01:01:36.900> these 01:01:37.040 --> 01:01:37.050 align:start position:0% for this if we treated any of these 01:01:37.050 --> 01:01:38.690 align:start position:0% for this if we treated any of these small<01:01:37.410> lot<01:01:37.650> size<01:01:37.950> as<01:01:38.220> some<01:01:38.460> type<01:01:38.670> of 01:01:38.690 --> 01:01:38.700 align:start position:0% small lot size as some type of 01:01:38.700 --> 01:01:42.580 align:start position:0% small lot size as some type of clustering<01:01:39.480> option<01:01:40.050> and<01:01:40.320> had<01:01:41.220> additional 01:01:42.580 --> 01:01:42.590 align:start position:0% clustering option and had additional 01:01:42.590 --> 01:01:45.710 align:start position:0% clustering option and had additional buffers<01:01:43.590> so<01:01:44.490> that<01:01:44.670> it<01:01:44.790> wasn't<01:01:45.150> obvious<01:01:45.390> that 01:01:45.710 --> 01:01:45.720 align:start position:0% buffers so that it wasn't obvious that 01:01:45.720 --> 01:01:47.570 align:start position:0% buffers so that it wasn't obvious that you<01:01:46.020> were<01:01:46.050> putting<01:01:46.680> something<01:01:47.070> that<01:01:47.370> just 01:01:47.570 --> 01:01:47.580 align:start position:0% you were putting something that just 01:01:47.580 --> 01:01:50.960 align:start position:0% you were putting something that just totally<01:01:47.850> didn't<01:01:48.600> fit<01:01:48.900> in<01:01:49.200> the<01:01:50.160> middle<01:01:50.370> of<01:01:50.430> you 01:01:50.960 --> 01:01:50.970 align:start position:0% totally didn't fit in the middle of you 01:01:50.970 --> 01:01:57.830 align:start position:0% totally didn't fit in the middle of you know<01:01:51.030> the<01:01:51.270> VL<01:01:51.540> dr<01:01:54.980> and<01:01:55.980> keep<01:01:56.430> it<01:01:56.640> on<01:01:56.820> i<01:01:57.240> can<01:01:57.660> just 01:01:57.830 --> 01:01:57.840 align:start position:0% know the VL dr and keep it on i can just 01:01:57.840 --> 01:02:02.780 align:start position:0% know the VL dr and keep it on i can just add<01:01:58.080> in<01:01:58.380> the<01:01:58.530> VL<01:01:58.800> dr<01:01:59.900> the<01:02:01.220> density<01:02:02.220> that<01:02:02.250> goes 01:02:02.780 --> 01:02:02.790 align:start position:0% add in the VL dr the density that goes 01:02:02.790 --> 01:02:04.610 align:start position:0% add in the VL dr the density that goes along<01:02:03.000> with<01:02:03.180> that<01:02:03.450> if<01:02:03.870> someone<01:02:04.170> were<01:02:04.440> to 01:02:04.610 --> 01:02:04.620 align:start position:0% along with that if someone were to 01:02:04.620 --> 01:02:07.190 align:start position:0% along with that if someone were to resent<01:02:05.010> is<01:02:05.160> less<01:02:05.400> than<01:02:05.580> one<01:02:05.790> unit<01:02:06.120> per<01:02:06.330> acre<01:02:06.750> so 01:02:07.190 --> 01:02:07.200 align:start position:0% resent is less than one unit per acre so 01:02:07.200 --> 01:02:12.950 align:start position:0% resent is less than one unit per acre so by<01:02:08.390> there's<01:02:09.390> going<01:02:09.690> to<01:02:09.780> be<01:02:09.950> a<01:02:11.570> significant<01:02:12.570> to 01:02:12.950 --> 01:02:12.960 align:start position:0% by there's going to be a significant to 01:02:12.960 --> 01:02:15.320 align:start position:0% by there's going to be a significant to have<01:02:13.530> if<01:02:13.800> you<01:02:14.040> were<01:02:14.070> to<01:02:14.340> have<01:02:14.550> lots<01:02:14.790> of<01:02:15.060> small 01:02:15.320 --> 01:02:15.330 align:start position:0% have if you were to have lots of small 01:02:15.330 --> 01:02:18.610 align:start position:0% have if you were to have lots of small as<01:02:15.510> 8,000<01:02:16.140> square<01:02:16.350> feet<01:02:16.560> there<01:02:16.800> would<01:02:16.950> be<01:02:16.980> some 01:02:18.610 --> 01:02:18.620 align:start position:0% as 8,000 square feet there would be some 01:02:18.620 --> 01:02:22.220 align:start position:0% as 8,000 square feet there would be some significant<01:02:19.620> open<01:02:19.950> space<01:02:20.610> within<01:02:21.480> the<01:02:22.020> area 01:02:22.220 --> 01:02:22.230 align:start position:0% significant open space within the area 01:02:22.230 --> 01:02:27.710 align:start position:0% significant open space within the area because<01:02:22.860> the<01:02:23.190> because<01:02:23.610> the<01:02:23.940> density<01:02:24.950> is<01:02:26.720> low 01:02:27.710 --> 01:02:27.720 align:start position:0% because the because the density is low 01:02:27.720 --> 01:02:31.730 align:start position:0% because the because the density is low normally<01:02:28.760> in<01:02:29.760> our<01:02:29.940> 40<01:02:30.540> disk<01:02:30.780> in<01:02:31.020> art<01:02:31.350> 40 01:02:31.730 --> 01:02:31.740 align:start position:0% normally in our 40 disk in art 40 01:02:31.740 --> 01:02:33.320 align:start position:0% normally in our 40 disk in art 40 district<01:02:32.220> for<01:02:32.400> example<01:02:32.850> of<01:02:32.970> where<01:02:33.180> the 01:02:33.320 --> 01:02:33.330 align:start position:0% district for example of where the 01:02:33.330 --> 01:02:35.480 align:start position:0% district for example of where the minimum<01:02:33.690> lot<01:02:33.810> size<01:02:33.870> is<01:02:34.110> 40,000<01:02:35.040> square<01:02:35.250> feet 01:02:35.480 --> 01:02:35.490 align:start position:0% minimum lot size is 40,000 square feet 01:02:35.490 --> 01:02:38.930 align:start position:0% minimum lot size is 40,000 square feet you<01:02:35.790> could<01:02:36.240> get<01:02:36.450> a<01:02:37.280> yield<01:02:38.280> of<01:02:38.400> one<01:02:38.610> unit<01:02:38.910> per 01:02:38.930 --> 01:02:38.940 align:start position:0% you could get a yield of one unit per 01:02:38.940 --> 01:02:41.180 align:start position:0% you could get a yield of one unit per acre<01:02:39.210> you<01:02:39.450> it<01:02:39.600> could<01:02:39.840> have<01:02:40.020> potential<01:02:40.710> roughly 01:02:41.180 --> 01:02:41.190 align:start position:0% acre you it could have potential roughly 01:02:41.190 --> 01:02:42.860 align:start position:0% acre you it could have potential roughly the<01:02:41.340> same<01:02:41.520> number<01:02:41.580> of<01:02:41.910> lines<01:02:42.180> so<01:02:42.570> there<01:02:42.750> would 01:02:42.860 --> 01:02:42.870 align:start position:0% the same number of lines so there would 01:02:42.870 --> 01:02:45.500 align:start position:0% the same number of lines so there would be<01:02:42.900> a<01:02:43.320> good<01:02:43.980> bit<01:02:44.190> of<01:02:44.220> area<01:02:44.910> that<01:02:45.090> would<01:02:45.210> be<01:02:45.390> in 01:02:45.500 --> 01:02:45.510 align:start position:0% be a good bit of area that would be in 01:02:45.510 --> 01:02:48.050 align:start position:0% be a good bit of area that would be in the<01:02:45.600> open<01:02:45.930> space<01:02:46.200> and<01:02:46.230> then<01:02:46.680> in<01:02:46.940> looking<01:02:47.940> at 01:02:48.050 --> 01:02:48.060 align:start position:0% the open space and then in looking at 01:02:48.060 --> 01:02:49.880 align:start position:0% the open space and then in looking at that<01:02:48.240> I<01:02:48.300> think<01:02:48.450> we<01:02:48.840> would<01:02:48.990> be<01:02:49.230> you<01:02:49.740> know 01:02:49.880 --> 01:02:49.890 align:start position:0% that I think we would be you know 01:02:49.890 --> 01:02:53.630 align:start position:0% that I think we would be you know seeking<01:02:50.310> to<01:02:50.400> try<01:02:50.610> to<01:02:51.710> you<01:02:52.710> know<01:02:52.740> maximize 01:02:53.630 --> 01:02:53.640 align:start position:0% seeking to try to you know maximize 01:02:53.640 --> 01:02:56.029 align:start position:0% seeking to try to you know maximize the<01:02:53.789> use<01:02:54.630> of<01:02:54.660> that<01:02:54.930> open<01:02:55.319> space<01:02:55.589> in<01:02:55.769> an 01:02:56.029 --> 01:02:56.039 align:start position:0% the use of that open space in an 01:02:56.039 --> 01:03:02.779 align:start position:0% the use of that open space in an appropriate<01:02:56.519> manner<01:03:01.369> if<01:03:02.369> memory<01:03:02.730> serves 01:03:02.779 --> 01:03:02.789 align:start position:0% appropriate manner if memory serves 01:03:02.789 --> 01:03:06.200 align:start position:0% appropriate manner if memory serves there<01:03:03.240> was<01:03:03.390> just<01:03:03.869> a<01:03:03.990> recent<01:03:04.730> case<01:03:05.730> where<01:03:06.029> that 01:03:06.200 --> 01:03:06.210 align:start position:0% there was just a recent case where that 01:03:06.210 --> 01:03:11.269 align:start position:0% there was just a recent case where that very<01:03:06.779> issue<01:03:06.960> was<01:03:07.970> was<01:03:08.970> very<01:03:09.269> uh<01:03:09.559> big<01:03:10.559> in<01:03:10.829> the<01:03:11.069> in 01:03:11.269 --> 01:03:11.279 align:start position:0% very issue was was very uh big in the in 01:03:11.279 --> 01:03:15.470 align:start position:0% very issue was was very uh big in the in the<01:03:11.309> decision<01:03:11.849> process<01:03:12.140> of<01:03:13.140> the<01:03:14.099> overall<01:03:14.480> why 01:03:15.470 --> 01:03:15.480 align:start position:0% the decision process of the overall why 01:03:15.480 --> 01:03:23.240 align:start position:0% the decision process of the overall why we're<01:03:15.750> all<01:03:15.869> over<01:03:16.260> by<01:03:16.410> 10<01:03:16.799> 10<01:03:17.099> somewhere<01:03:17.670> yep<01:03:22.250> do 01:03:23.240 --> 01:03:23.250 align:start position:0% we're all over by 10 10 somewhere yep do 01:03:23.250 --> 01:03:24.890 align:start position:0% we're all over by 10 10 somewhere yep do I<01:03:23.309> have<01:03:23.430> any<01:03:23.490> other<01:03:23.700> questions<01:03:24.450> that<01:03:24.809> you 01:03:24.890 --> 01:03:24.900 align:start position:0% I have any other questions that you 01:03:24.900 --> 01:03:27.730 align:start position:0% I have any other questions that you would<01:03:24.990> like<01:03:25.049> to<01:03:25.200> ask<01:03:25.410> him<01:03:25.650> a<01:03:25.740> Spearman<01:03:26.250> if<01:03:26.430> not 01:03:27.730 --> 01:03:27.740 align:start position:0% would like to ask him a Spearman if not 01:03:27.740 --> 01:03:30.140 align:start position:0% would like to ask him a Spearman if not would<01:03:28.740> someone<01:03:29.130> care<01:03:29.279> to<01:03:29.339> make<01:03:29.549> a<01:03:29.579> motion<01:03:29.849> one 01:03:30.140 --> 01:03:30.150 align:start position:0% would someone care to make a motion one 01:03:30.150 --> 01:03:39.160 align:start position:0% would someone care to make a motion one way<01:03:30.329> or<01:03:30.510> the<01:03:30.539> other<01:03:36.559> anyone<01:03:37.559> anyone<01:03:38.309> at<01:03:38.579> all 01:03:39.160 --> 01:03:39.170 align:start position:0% way or the other anyone anyone at all 01:03:39.170 --> 01:03:43.160 align:start position:0% way or the other anyone anyone at all thank<01:03:40.170> you<01:03:40.230> make<01:03:40.319> a<01:03:40.349> motion<01:03:41.029> and<01:03:42.029> we'll<01:03:42.990> move 01:03:43.160 --> 01:03:43.170 align:start position:0% thank you make a motion and we'll move 01:03:43.170 --> 01:03:49.299 align:start position:0% thank you make a motion and we'll move that<01:03:43.589> the<01:03:43.619> board<01:03:43.769> forward<01:03:44.490> ldo<01:03:44.970> amendment 01:03:49.299 --> 01:03:49.309 align:start position:0% 01:03:49.309 --> 01:03:54.049 align:start position:0% amendment<01:03:50.309> round<01:03:50.880> 31<01:03:51.569> item<01:03:52.200> c2<01:03:52.799> town<01:03:53.670> council 01:03:54.049 --> 01:03:54.059 align:start position:0% amendment round 31 item c2 town council 01:03:54.059 --> 01:03:56.299 align:start position:0% amendment round 31 item c2 town council with<01:03:54.150> a<01:03:54.210> recommendation<01:03:54.510> for<01:03:54.960> approval<01:03:55.380> as<01:03:55.559> it 01:03:56.299 --> 01:03:56.309 align:start position:0% with a recommendation for approval as it 01:03:56.309 --> 01:03:57.529 align:start position:0% with a recommendation for approval as it is<01:03:56.400> consistent<01:03:56.970> with<01:03:57.000> the<01:03:57.180> comprehensive 01:03:57.529 --> 01:03:57.539 align:start position:0% is consistent with the comprehensive 01:03:57.539 --> 01:04:00.289 align:start position:0% is consistent with the comprehensive plan<01:03:57.839> and<01:03:58.349> all<01:03:58.650> other<01:03:58.950> applicable<01:03:59.250> plans<01:03:59.730> and 01:04:00.289 --> 01:04:00.299 align:start position:0% plan and all other applicable plans and 01:04:00.299 --> 01:04:01.819 align:start position:0% plan and all other applicable plans and is<01:04:00.390> reasonable<01:04:00.960> and<01:04:01.079> in<01:04:01.319> the<01:04:01.410> public<01:04:01.710> interest 01:04:01.819 --> 01:04:01.829 align:start position:0% is reasonable and in the public interest 01:04:01.829 --> 01:04:03.650 align:start position:0% is reasonable and in the public interest for<01:04:02.369> the<01:04:02.460> reasons<01:04:02.789> set<01:04:02.940> forth<01:04:03.000> in<01:04:03.329> the<01:04:03.390> staff 01:04:03.650 --> 01:04:03.660 align:start position:0% for the reasons set forth in the staff 01:04:03.660 --> 01:04:07.880 align:start position:0% for the reasons set forth in the staff report<01:04:03.809> and<01:04:04.140> presentation<01:04:06.740> there<01:04:07.740> is<01:04:07.859> a 01:04:07.880 --> 01:04:07.890 align:start position:0% report and presentation there is a 01:04:07.890 --> 01:04:12.009 align:start position:0% report and presentation there is a motion<01:04:08.279> is<01:04:08.400> there<01:04:08.519> a<01:04:08.579> second<01:04:09.529> that's<01:04:10.529> second 01:04:12.009 --> 01:04:12.019 align:start position:0% motion is there a second that's second 01:04:12.019 --> 01:04:16.279 align:start position:0% motion is there a second that's second discussion<01:04:13.019> please<01:04:14.450> I'm<01:04:15.450> total<01:04:15.839> support<01:04:16.079> for 01:04:16.279 --> 01:04:16.289 align:start position:0% discussion please I'm total support for 01:04:16.289 --> 01:04:18.589 align:start position:0% discussion please I'm total support for this<01:04:16.380> I<01:04:16.890> honestly<01:04:17.579> don't<01:04:18.119> think<01:04:18.210> that<01:04:18.480> there's 01:04:18.589 --> 01:04:18.599 align:start position:0% this I honestly don't think that there's 01:04:18.599 --> 01:04:20.990 align:start position:0% this I honestly don't think that there's any<01:04:18.869> reason<01:04:19.109> why<01:04:19.380> we<01:04:19.769> would<01:04:19.950> ever<01:04:20.130> have<01:04:20.400> a<01:04:20.640> TR 01:04:20.990 --> 01:04:21.000 align:start position:0% any reason why we would ever have a TR 01:04:21.000 --> 01:04:23.509 align:start position:0% any reason why we would ever have a TR in<01:04:21.269> an<01:04:21.509> LDR<01:04:21.990> bldr<01:04:22.799> I<01:04:22.980> just<01:04:23.160> don't<01:04:23.279> think<01:04:23.460> it 01:04:23.509 --> 01:04:23.519 align:start position:0% in an LDR bldr I just don't think it 01:04:23.519 --> 01:04:25.460 align:start position:0% in an LDR bldr I just don't think it makes<01:04:23.670> sense<01:04:23.759> I<01:04:24.299> just<01:04:24.690> picture<01:04:24.960> cases<01:04:25.319> where 01:04:25.460 --> 01:04:25.470 align:start position:0% makes sense I just picture cases where 01:04:25.470 --> 01:04:27.140 align:start position:0% makes sense I just picture cases where you<01:04:25.500> have<01:04:25.589> in<01:04:25.890> our<01:04:25.980> for<01:04:26.250> deer<01:04:26.400> in<01:04:26.490> our<01:04:26.609> 20<01:04:26.970> and 01:04:27.140 --> 01:04:27.150 align:start position:0% you have in our for deer in our 20 and 01:04:27.150 --> 01:04:29.299 align:start position:0% you have in our for deer in our 20 and you<01:04:27.240> come<01:04:27.480> in<01:04:27.630> with<01:04:27.660> this<01:04:27.900> really<01:04:28.319> close<01:04:28.559> 5,000 01:04:29.299 --> 01:04:29.309 align:start position:0% you come in with this really close 5,000 01:04:29.309 --> 01:04:31.130 align:start position:0% you come in with this really close 5,000 square<01:04:29.490> foot<01:04:29.640> lots<01:04:29.880> and<01:04:30.269> that<01:04:30.750> to<01:04:30.869> me<01:04:30.960> makes 01:04:31.130 --> 01:04:31.140 align:start position:0% square foot lots and that to me makes 01:04:31.140 --> 01:04:32.480 align:start position:0% square foot lots and that to me makes absolutely<01:04:31.710> no<01:04:31.769> sense<01:04:31.829> from<01:04:32.130> a<01:04:32.190> planning 01:04:32.480 --> 01:04:32.490 align:start position:0% absolutely no sense from a planning 01:04:32.490 --> 01:04:34.519 align:start position:0% absolutely no sense from a planning perspective<01:04:32.519> so<01:04:33.420> I'm<01:04:33.690> in<01:04:33.869> total<01:04:34.019> support<01:04:34.319> for 01:04:34.519 --> 01:04:34.529 align:start position:0% perspective so I'm in total support for 01:04:34.529 --> 01:04:40.670 align:start position:0% perspective so I'm in total support for this<01:04:34.619> I<01:04:36.589> agree<01:04:37.589> i<01:04:37.619> think<01:04:38.390> town<01:04:39.529> counts<01:04:40.529> our 01:04:40.670 --> 01:04:40.680 align:start position:0% this I agree i think town counts our 01:04:40.680 --> 01:04:43.059 align:start position:0% this I agree i think town counts our town<01:04:41.130> staff<01:04:41.400> did<01:04:41.609> a<01:04:41.640> good<01:04:41.759> job<01:04:41.819> of<01:04:42.049> recognizing 01:04:43.059 --> 01:04:43.069 align:start position:0% town staff did a good job of recognizing 01:04:43.069 --> 01:04:44.599 align:start position:0% town staff did a good job of recognizing considerations<01:04:44.069> and<01:04:44.220> making<01:04:44.519> the 01:04:44.599 --> 01:04:44.609 align:start position:0% considerations and making the 01:04:44.609 --> 01:04:48.170 align:start position:0% considerations and making the appropriate<01:04:44.789> judgment<01:04:45.240> sir<01:04:45.599> so<01:04:45.930> i'm<01:04:46.650> in<01:04:46.799> favor 01:04:48.170 --> 01:04:48.180 align:start position:0% appropriate judgment sir so i'm in favor 01:04:48.180 --> 01:04:51.380 align:start position:0% appropriate judgment sir so i'm in favor any<01:04:49.020> other<01:04:49.260> discussion<01:04:49.700> well<01:04:50.700> I'm<01:04:51.089> going<01:04:51.270> to 01:04:51.380 --> 01:04:51.390 align:start position:0% any other discussion well I'm going to 01:04:51.390 --> 01:04:53.720 align:start position:0% any other discussion well I'm going to vote<01:04:51.540> against<01:04:51.930> the<01:04:51.990> motion<01:04:52.069> this<01:04:53.069> is<01:04:53.250> my<01:04:53.490> knife 01:04:53.720 --> 01:04:53.730 align:start position:0% vote against the motion this is my knife 01:04:53.730 --> 01:04:58.730 align:start position:0% vote against the motion this is my knife to<01:04:54.180> just<01:04:54.420> say<01:04:54.630> that<01:04:55.040> I<01:04:56.660> I<01:04:57.660> think<01:04:58.109> that<01:04:58.200> we 01:04:58.730 --> 01:04:58.740 align:start position:0% to just say that I I think that we 01:04:58.740 --> 01:05:01.309 align:start position:0% to just say that I I think that we should<01:04:58.770> not<01:04:59.099> be<01:04:59.309> looking<01:04:59.700> at<01:04:59.849> lot<01:05:00.059> size<01:05:00.390> or<01:05:00.750> lot 01:05:01.309 --> 01:05:01.319 align:start position:0% should not be looking at lot size or lot 01:05:01.319 --> 01:05:03.920 align:start position:0% should not be looking at lot size or lot sizes<01:05:01.890> less<01:05:02.130> than<01:05:02.369> 15,000<01:05:03.210> square<01:05:03.450> feet<01:05:03.690> in 01:05:03.920 --> 01:05:03.930 align:start position:0% sizes less than 15,000 square feet in 01:05:03.930 --> 01:05:07.040 align:start position:0% sizes less than 15,000 square feet in the<01:05:04.170> VL<01:05:04.500> dr<01:05:04.920> without<01:05:05.849> additional<01:05:06.420> buffer 01:05:07.040 --> 01:05:07.050 align:start position:0% the VL dr without additional buffer 01:05:07.050 --> 01:05:10.460 align:start position:0% the VL dr without additional buffer protections<01:05:07.710> and<01:05:09.050> you<01:05:10.050> know<01:05:10.140> we<01:05:10.260> didn't 01:05:10.460 --> 01:05:10.470 align:start position:0% protections and you know we didn't 01:05:10.470 --> 01:05:15.410 align:start position:0% protections and you know we didn't really<01:05:10.500> focus<01:05:10.980> on<01:05:11.339> ldr<01:05:12.200> but<01:05:14.089> you<01:05:15.089> know<01:05:15.210> I<01:05:15.240> think 01:05:15.410 --> 01:05:15.420 align:start position:0% really focus on ldr but you know I think 01:05:15.420 --> 01:05:19.270 align:start position:0% really focus on ldr but you know I think that<01:05:15.960> we<01:05:16.260> should<01:05:17.390> you<01:05:18.390> know<01:05:18.420> build<01:05:18.990> in 01:05:19.270 --> 01:05:19.280 align:start position:0% that we should you know build in 01:05:19.280 --> 01:05:22.549 align:start position:0% that we should you know build in appropriate<01:05:20.280> buffers<01:05:20.910> to<01:05:21.200> accommodate<01:05:22.200> these 01:05:22.549 --> 01:05:22.559 align:start position:0% appropriate buffers to accommodate these 01:05:22.559 --> 01:05:25.880 align:start position:0% appropriate buffers to accommodate these I<01:05:22.829> think<01:05:22.920> are<01:05:23.280> eats<01:05:23.490> already<01:05:23.849> allowed<01:05:24.690> in<01:05:24.890> it's 01:05:25.880 --> 01:05:25.890 align:start position:0% I think are eats already allowed in it's 01:05:25.890 --> 01:05:28.940 align:start position:0% I think are eats already allowed in it's already<01:05:26.130> already<01:05:26.520> allowed<01:05:26.880> an<01:05:27.059> ldr<01:05:27.540> I<01:05:27.950> guess 01:05:28.940 --> 01:05:28.950 align:start position:0% already already allowed an ldr I guess 01:05:28.950 --> 01:05:31.400 align:start position:0% already already allowed an ldr I guess anything<01:05:29.400> is<01:05:29.520> that's<01:05:29.819> anyway<01:05:30.270> right<01:05:30.690> right<01:05:30.930> ok 01:05:31.400 --> 01:05:31.410 align:start position:0% anything is that's anyway right right ok 01:05:31.410 --> 01:05:36.710 align:start position:0% anything is that's anyway right right ok I<01:05:31.880> mean<01:05:32.880> that's<01:05:34.220> well<01:05:35.220> for<01:05:35.430> sure<01:05:35.460> in<01:05:35.940> the<01:05:36.089> VL<01:05:36.359> dr 01:05:36.710 --> 01:05:36.720 align:start position:0% I mean that's well for sure in the VL dr 01:05:36.720 --> 01:05:39.470 align:start position:0% I mean that's well for sure in the VL dr i<01:05:37.040> believe<01:05:38.040> we<01:05:38.190> need<01:05:38.400> additional<01:05:38.940> buffer 01:05:39.470 --> 01:05:39.480 align:start position:0% i believe we need additional buffer 01:05:39.480 --> 01:05:41.150 align:start position:0% i believe we need additional buffer protections<01:05:40.020> I<01:05:40.140> don't<01:05:40.319> think<01:05:40.470> r8<01:05:40.770> belongs 01:05:41.150 --> 01:05:41.160 align:start position:0% protections I don't think r8 belongs 01:05:41.160 --> 01:05:43.069 align:start position:0% protections I don't think r8 belongs there<01:05:41.460> at<01:05:41.579> all<01:05:41.700> but<01:05:41.970> if<01:05:42.059> it<01:05:42.180> does<01:05:42.390> we<01:05:42.780> really 01:05:43.069 --> 01:05:43.079 align:start position:0% there at all but if it does we really 01:05:43.079 --> 01:05:45.020 align:start position:0% there at all but if it does we really need<01:05:43.230> to<01:05:43.349> be<01:05:43.500> fed<01:05:43.710> the<01:05:43.980> buffers<01:05:44.339> around<01:05:44.700> it<01:05:44.880> and 01:05:45.020 --> 01:05:45.030 align:start position:0% need to be fed the buffers around it and 01:05:45.030 --> 01:05:50.690 align:start position:0% need to be fed the buffers around it and there<01:05:45.780> are<01:05:45.900> 12<01:05:46.230> is<01:05:46.579> basically<01:05:47.579> the<01:05:47.760> same<01:05:49.700> since 01:05:50.690 --> 01:05:50.700 align:start position:0% there are 12 is basically the same since 01:05:50.700 --> 01:05:52.099 align:start position:0% there are 12 is basically the same since that<01:05:50.849> was<01:05:50.970> my<01:05:51.089> original<01:05:51.150> question<01:05:51.480> I<01:05:51.839> have<01:05:51.990> to 01:05:52.099 --> 01:05:52.109 align:start position:0% that was my original question I have to 01:05:52.109 --> 01:05:54.500 align:start position:0% that was my original question I have to agree<01:05:52.200> and<01:05:53.130> I<01:05:53.220> know<01:05:53.280> mathematically<01:05:54.000> it 01:05:54.500 --> 01:05:54.510 align:start position:0% agree and I know mathematically it 01:05:54.510 --> 01:05:55.789 align:start position:0% agree and I know mathematically it figures<01:05:54.900> out<01:05:55.020> that<01:05:55.079> there<01:05:55.349> will<01:05:55.500> be<01:05:55.530> other 01:05:55.789 --> 01:05:55.799 align:start position:0% figures out that there will be other 01:05:55.799 --> 01:05:58.329 align:start position:0% figures out that there will be other leftover<01:05:56.549> spaces<01:05:57.000> but<01:05:57.240> just<01:05:57.599> extra 01:05:58.329 --> 01:05:58.339 align:start position:0% leftover spaces but just extra 01:05:58.339 --> 01:06:00.319 align:start position:0% leftover spaces but just extra expectations<01:05:59.339> or<01:05:59.520> verbiage<01:05:59.910> and<01:06:00.030> that<01:06:00.210> would 01:06:00.319 --> 01:06:00.329 align:start position:0% expectations or verbiage and that would 01:06:00.329 --> 01:06:03.049 align:start position:0% expectations or verbiage and that would help<01:06:00.420> all<01:06:00.660> right<01:06:01.349> you<01:06:01.770> forgot<01:06:02.130> was<01:06:02.430> lot<01:06:02.790> size 01:06:03.049 --> 01:06:03.059 align:start position:0% help all right you forgot was lot size 01:06:03.059 --> 01:06:08.780 align:start position:0% help all right you forgot was lot size expectations<01:06:03.990> we<01:06:04.200> didn't<01:06:04.470> hit<01:06:04.589> the<01:06:04.740> mark<01:06:07.790> any 01:06:08.780 --> 01:06:08.790 align:start position:0% expectations we didn't hit the mark any 01:06:08.790 --> 01:06:12.799 align:start position:0% expectations we didn't hit the mark any other<01:06:08.970> discussion<01:06:10.849> if<01:06:11.849> not<01:06:12.150> that<01:06:12.359> I<01:06:12.450> will<01:06:12.599> call 01:06:12.799 --> 01:06:12.809 align:start position:0% other discussion if not that I will call 01:06:12.809 --> 01:06:15.049 align:start position:0% other discussion if not that I will call a<01:06:12.839> vote<01:06:13.049> on<01:06:13.109> this<01:06:13.349> all<01:06:13.559> those<01:06:13.740> in<01:06:13.890> favor<01:06:14.130> of<01:06:14.460> the 01:06:15.049 --> 01:06:15.059 align:start position:0% a vote on this all those in favor of the 01:06:15.059 --> 01:06:17.120 align:start position:0% a vote on this all those in favor of the motion<01:06:15.240> to<01:06:15.540> approve<01:06:15.750> this<01:06:16.140> ldo<01:06:16.650> amendment 01:06:17.120 --> 01:06:17.130 align:start position:0% motion to approve this ldo amendment 01:06:17.130 --> 01:06:20.359 align:start position:0% motion to approve this ldo amendment please<01:06:17.220> say<01:06:17.549> aye<01:06:17.660> hi<01:06:18.859> anyone<01:06:19.859> opposed<01:06:20.099> please 01:06:20.359 --> 01:06:20.369 align:start position:0% please say aye hi anyone opposed please 01:06:20.369 --> 01:06:25.220 align:start position:0% please say aye hi anyone opposed please say<01:06:20.520> no<01:06:20.670> no<01:06:21.119> oh<01:06:21.359> I<01:06:21.930> have<01:06:22.319> three<01:06:22.589> knows<01:06:24.049> so<01:06:25.049> we're 01:06:25.220 --> 01:06:25.230 align:start position:0% say no no oh I have three knows so we're 01:06:25.230 --> 01:06:29.410 align:start position:0% say no no oh I have three knows so we're 523<01:06:25.950> on<01:06:26.069> that<01:06:26.299> for<01:06:27.299> three<01:06:27.569> for<01:06:27.900> three<01:06:28.079> for<01:06:28.980> two 01:06:29.410 --> 01:06:29.420 align:start position:0% 523 on that for three for three for two 01:06:29.420 --> 01:06:31.789 align:start position:0% 523 on that for three for three for two years<01:06:30.420> with<01:06:30.599> a<01:06:30.750> lie<01:06:30.809> never<01:06:31.140> saw<01:06:31.380> four<01:06:31.710> two 01:06:31.789 --> 01:06:31.799 align:start position:0% years with a lie never saw four two 01:06:31.799 --> 01:06:38.680 align:start position:0% years with a lie never saw four two three<01:06:31.920> one<01:06:32.309> two<01:06:32.930> of<01:06:33.930> them<01:06:36.980> we<01:06:37.980> come<01:06:38.220> out<01:06:38.339> there 01:06:38.680 --> 01:06:38.690 align:start position:0% three one two of them we come out there 01:06:38.690 --> 01:06:41.359 align:start position:0% three one two of them we come out there that<01:06:39.690> concludes<01:06:39.900> this<01:06:40.319> business<01:06:40.770> the<01:06:41.010> next 01:06:41.359 --> 01:06:41.369 align:start position:0% that concludes this business the next 01:06:41.369 --> 01:06:43.700 align:start position:0% that concludes this business the next item<01:06:41.910> on<01:06:42.240> our<01:06:42.839> agendas<01:06:43.260> are<01:06:43.349> new<01:06:43.500> and<01:06:43.589> old 01:06:43.700 --> 01:06:43.710 align:start position:0% item on our agendas are new and old 01:06:43.710 --> 01:06:45.890 align:start position:0% item on our agendas are new and old business<01:06:44.040> I<01:06:44.190> don't<01:06:44.369> know<01:06:44.520> if<01:06:44.700> any<01:06:44.910> no<01:06:45.630> one<01:06:45.750> else 01:06:45.890 --> 01:06:45.900 align:start position:0% business I don't know if any no one else 01:06:45.900 --> 01:06:49.460 align:start position:0% business I don't know if any no one else does<01:06:46.170> and<01:06:47.180> defense<01:06:48.180> the<01:06:48.359> case<01:06:48.569> i<01:06:48.869> motion<01:06:49.440> to 01:06:49.460 --> 01:06:49.470 align:start position:0% does and defense the case i motion to 01:06:49.470 --> 01:06:52.069 align:start position:0% does and defense the case i motion to adjourn<01:06:50.390> we<01:06:51.390> have<01:06:51.480> a<01:06:51.510> motion<01:06:51.780> to<01:06:51.960> adjourn 01:06:52.069 --> 01:06:52.079 align:start position:0% adjourn we have a motion to adjourn 01:06:52.079 --> 01:06:56.950 align:start position:0% adjourn we have a motion to adjourn let's<01:06:52.950> see<01:06:53.099> this<01:06:53.220> one<01:06:53.400> before<01:06:53.579> 23<01:06:54.089> all<01:06:54.210> those 01:06:56.950 --> 01:06:56.960 align:start position:0% 01:06:56.960 --> 01:07:56.340 align:start position:0% opposed<01:06:58.220> thank<01:06:59.220> you 01:07:56.340 --> 01:07:56.350 align:start position:0% 01:07:56.350 --> 01:07:58.990 align:start position:0% this<01:07:57.350> has<01:07:57.590> been<01:07:57.740> a<01:07:57.800> production<01:07:57.950> of<01:07:58.310> Harry<01:07:58.580> TV 01:07:58.990 --> 01:07:59.000 align:start position:0% this has been a production of Harry TV 01:07:59.000 --> 01:08:15.630 align:start position:0% this has been a production of Harry TV visit<01:07:59.869> the<01:07:59.960> town<01:08:00.110> of<01:08:00.260> rough<01:08:00.740> selective<01:08:01.250> time 01:08:15.630 --> 01:08:15.640 align:start position:0% 01:08:15.640 --> 01:08:17.700 align:start position:0% you